From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] pstore: migrate to crypto acomp interface (take 2)
Date: Mon, 17 Oct 2022 18:25:01 -0300 [thread overview]
Message-ID: <dbcc136d-7993-884e-f1de-ac696ae4bd0f@igalia.com> (raw)
In-Reply-To: <CAMj1kXGA=kBdahDTuFDPzZKf5bbvxH2Ns7Ows+5D-PAx8rwP2w@mail.gmail.com>
On 17/10/2022 18:16, Ard Biesheuvel wrote:
> On Mon, 17 Oct 2022 at 23:10, Guilherme G. Piccoli <gpiccoli@igalia.com> wrote:
>> [...]
>> Out of curiosity, do you have a number here, like X kilobytes per active
>> CPU?
>
> 2x128 KB per CPU, which makes 128 KB also the maximum input/output
> size per request when using this interface. (SCOMP_SCRATCH_SIZE)
>
> On my 32x4 CPU workstation, this amounts to 32 MB permanently locked
> up for nothing when the pstore driver is loaded (with compression
> enabled)
Thanks! This is really something...
prev parent reply other threads:[~2022-10-17 21:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 23:41 Kees Cook
2022-10-06 23:45 ` Kees Cook
2022-10-07 18:46 ` Guilherme G. Piccoli
2022-10-17 16:26 ` Guilherme G. Piccoli
2022-10-17 18:01 ` Kees Cook
2022-10-17 18:14 ` Ard Biesheuvel
2022-10-17 18:22 ` Guilherme G. Piccoli
2022-10-17 19:11 ` Ard Biesheuvel
2022-10-17 19:29 ` Kees Cook
2022-10-17 19:33 ` Ard Biesheuvel
2022-10-17 19:40 ` Kees Cook
2022-10-17 19:45 ` Ard Biesheuvel
2022-10-17 20:11 ` Kees Cook
2022-10-17 20:13 ` Ard Biesheuvel
2022-10-17 20:35 ` Kees Cook
2022-10-17 21:01 ` Ard Biesheuvel
2022-10-17 21:10 ` Guilherme G. Piccoli
2022-10-17 21:16 ` Ard Biesheuvel
2022-10-17 21:25 ` Guilherme G. Piccoli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dbcc136d-7993-884e-f1de-ac696ae4bd0f@igalia.com \
--to=gpiccoli@igalia.com \
--cc=anton@enomsg.org \
--cc=ardb@kernel.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®