From: David Sterba <dsterba@suse.cz>
To: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
ardb@kernel.org, kees@kernel.org, linux-kernel@vger.kernel.org,
enlin.mu@unisoc.com, ebiggers@google.com, gpiccoli@igalia.com,
willy@infradead.org, yunlong.xing@unisoc.com,
yuxiaozhang@google.com, qat-linux@intel.com,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Yang Shen <shenyang39@huawei.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Weigang Li <weigang.li@intel.com>, Chris Mason <clm@meta.com>,
Brian Will <brian.will@intel.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/4] crypto: qat - Remove zlib-deflate
Date: Tue, 5 Sep 2023 18:23:02 +0200 [thread overview]
Message-ID: <20230905162302.GD14420@twin.jikos.cz> (raw)
In-Reply-To: <ZPcqALQ0Ck/3lF0U@gcabiddu-mobl1.ger.corp.intel.com>
On Tue, Sep 05, 2023 at 02:15:44PM +0100, Giovanni Cabiddu wrote:
> Hi Herbert,
>
> On Wed, Aug 30, 2023 at 06:08:47PM +0800, Herbert Xu wrote:
> > Remove the implementation of zlib-deflate because it is completely
> > unused in the kernel.
> We are working at a new revision of [1] which enables BTRFS to use acomp
> for offloading zlib-deflate. We see that there is value in using QAT for
> such use case in terms of throughput / CPU utilization / compression ratio
> compared to software.
> Zlib-deflate is preferred to deflate since BTRFS already uses that
> format.
>
> We expect to send this patch for 6.7.
> Can we keep zlib-deflate in the kernel?
>
> Thanks,
>
> [1] https://patchwork.kernel.org/project/linux-btrfs/patch/1467083180-111750-1-git-send-email-weigang.li@intel.com/
The patch is from 2016 and zlib though still supported has been
superseded by zstd that is from 2017. It would be good to see numbers
comparing zlib (cpu), zlib (qat) against relevant zstd levels. The
offloading might be an improvement and worth adding the support
otherwise I don't see much reason to add it unless there are users.
I can see there's QAT support for zstd too,
https://github.com/intel/QAT-ZSTD-Plugin, can't find one for lzo but in
case ther's QAT for all 3 algorithms used by btrfs I wouldn't mind
keeping the QAT support for zlib for parity.
next prev parent reply other threads:[~2023-09-05 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgaY2+_KyqVpRS+MrO6Y7bXQp69odTu7JT3XSpdUsgS=g@mail.gmail.com>
[not found] ` <ZO8HcBirOZnX9iRs@gondor.apana.org.au>
2023-08-30 10:04 ` [PATCH 0/4] crypto: Remove zlib-deflate Herbert Xu
2023-08-30 10:08 ` [PATCH 1/4] crypto: hisilicon/zip - Remove driver Herbert Xu
2023-08-31 2:21 ` Yang Shen
2023-08-31 5:42 ` Herbert Xu
2023-08-31 9:39 ` Yang Shen
2023-08-31 11:57 ` Herbert Xu
2023-08-30 10:08 ` [PATCH 2/4] crypto: qat - Remove zlib-deflate Herbert Xu
2023-09-05 13:15 ` Giovanni Cabiddu
2023-09-05 16:23 ` David Sterba [this message]
2023-09-06 2:51 ` Gao Xiang
2023-08-30 10:08 ` [PATCH 3/4] crypto: deflate " Herbert Xu
2023-08-30 10:08 ` [PATCH 4/4] crypto: testmgr " Herbert Xu
2023-08-30 12:52 ` [PATCH 0/4] crypto: " Ard Biesheuvel
2023-08-30 15:29 ` Linus Torvalds
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=20230905162302.GD14420@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ardb@kernel.org \
--cc=brian.will@intel.com \
--cc=clm@meta.com \
--cc=ebiggers@google.com \
--cc=enlin.mu@unisoc.com \
--cc=giovanni.cabiddu@intel.com \
--cc=gpiccoli@igalia.com \
--cc=herbert@gondor.apana.org.au \
--cc=kees@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=shenyang39@huawei.com \
--cc=torvalds@linux-foundation.org \
--cc=wangzhou1@hisilicon.com \
--cc=weigang.li@intel.com \
--cc=willy@infradead.org \
--cc=yunlong.xing@unisoc.com \
--cc=yuxiaozhang@google.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