[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dbcc136d-7993-884e-f1de-ac696ae4bd0f@igalia.com>
Date: Mon, 17 Oct 2022 18:25:01 -0300
From: "Guilherme G. Piccoli" <gpiccoli@...lia.com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Kees Cook <keescook@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] pstore: migrate to crypto acomp interface (take 2)
On 17/10/2022 18:16, Ard Biesheuvel wrote:
> On Mon, 17 Oct 2022 at 23:10, Guilherme G. Piccoli <gpiccoli@...lia.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...
Powered by blists - more mailing lists