Skip to content

pstore: Use zstd directly by default for compression

Kees Cook linux-hardening lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest5 patches 3 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5pstore: Remove worse-case compression size logicfs/pstore/platform.c+9 -1350 replies
2/5pstore: Allow for arbitrary compression algorithmfs/pstore/Kconfig fs/pstore/platform.c+47 -1140 replies
3/5pstore: Use size_t for compress/decompression type widthsfs/pstore/platform.c+32 -150 replies
4/5pstore: Refactor compression initializationfs/pstore/platform.c+43 -280 replies
5/5pstore: Use zstd directly by default for compressionfs/pstore/Kconfig fs/pstore/platform.c+97 -70 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/5] pstore: Use zstd directly by default for compression

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(-)
Signature · 1 line
2.34.1