From: Kees Cook <keescook@chromium.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Nick Terrell <terrelln@fb.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: [PATCH 0/5] pstore: Use zstd directly by default for compression
Date: Mon, 17 Oct 2022 19:08:08 -0700 [thread overview]
Message-ID: <20221018020519.never.337-kees@kernel.org> (raw)
Hi,
Okay, here is a very lightly tested version of using zstd directly, which
should save 128KB per CPU compare to using crypto API. This leaves the
crypto API available, though, if someone wants to use it instead. Even
supporting both, this is a net reduction in code, due to dropping all
the zbufsize logic.
How does this look?
-Kees
Kees Cook (5):
pstore: Remove worse-case compression size logic
pstore: Allow for arbitrary compression algorithm
pstore: Use size_t for compress/decompression type widths
pstore: Refactor compression initialization
pstore: Use zstd directly by default for compression
fs/pstore/Kconfig | 131 +++++-----------
fs/pstore/platform.c | 358 ++++++++++++++++++++-----------------------
2 files changed, 209 insertions(+), 280 deletions(-)
--
2.34.1
next reply other threads:[~2022-10-18 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 2:08 Kees Cook [this message]
2022-10-18 2:08 ` [PATCH 1/5] pstore: Remove worse-case compression size logic Kees Cook
2022-10-18 2:08 ` [PATCH 2/5] pstore: Allow for arbitrary compression algorithm Kees Cook
2022-10-18 2:08 ` [PATCH 3/5] pstore: Use size_t for compress/decompression type widths Kees Cook
2022-10-18 2:08 ` [PATCH 4/5] pstore: Refactor compression initialization Kees Cook
2022-10-18 2:08 ` [PATCH 5/5] pstore: Use zstd directly by default for compression Kees Cook
2022-10-18 8:20 ` [PATCH 0/5] " Ard Biesheuvel
2022-10-18 14:10 ` Guilherme G. Piccoli
2022-10-18 14:38 ` Ard Biesheuvel
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=20221018020519.never.337-kees@kernel.org \
--to=keescook@chromium.org \
--cc=ardb@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrelln@fb.com \
--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