From: Gao Xiang <xiang@kernel.org>
To: Bo Liu <liubo03@inspur.com>
Cc: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9] erofs: support deflate decompress by using Intel QAT
Date: Thu, 22 May 2025 21:57:51 +0800 [thread overview]
Message-ID: <aC8tX4u/EFe8XsVP@debian> (raw)
In-Reply-To: <2f0e05c0-fe6b-4e84-9ef5-c33ecc43d81c@linux.alibaba.com>
On Thu, May 22, 2025 at 05:52:32PM +0800, Gao Xiang wrote:
>
>
> On 2025/5/22 17:49, Bo Liu wrote:
> > This patch introdueces the use of the Intel QAT to decompress compressed
> > data in the EROFS filesystem, aiming to improve the decompression speed
> > of compressed datea.
> >
> > We created a 285MiB compressed file and then used the following command to
> > create EROFS images with different cluster size.
> > # mkfs.erofs -zdeflate,level=9 -C16384
> >
> > fio command was used to test random read and small random read(~5%) and
> > sequential read performance.
> > # fio -filename=testfile -bs=4k -rw=read -name=job1
> > # fio -filename=testfile -bs=4k -rw=randread -name=job1
> > # fio -filename=testfile -bs=4k -rw=randread --io_size=14m -name=job1
> >
> > Here are some performance numbers for reference:
> >
> > Processors: Intel(R) Xeon(R) 6766E(144 core)
> > Memory: 521 GiB
> >
> > |-----------------------------------------------------------------------------|
> > | | Cluster size | sequential read | randread | small randread(5%) |
> > |-----------|--------------|-----------------|-----------|--------------------|
> > | Intel QAT | 4096 | 538 MiB/s | 112 MiB/s | 20.76 MiB/s |
> > | Intel QAT | 16384 | 699 MiB/s | 158 MiB/s | 21.02 MiB/s |
> > | Intel QAT | 65536 | 917 MiB/s | 278 MiB/s | 20.90 MiB/s |
> > | Intel QAT | 131072 | 1056 MiB/s | 351 MiB/s | 23.36 MiB/s |
> > | Intel QAT | 262144 | 1145 MiB/s | 431 MiB/s | 26.66 MiB/s |
> > | deflate | 4096 | 499 MiB/s | 108 MiB/s | 21.50 MiB/s |
> > | deflate | 16384 | 422 MiB/s | 125 MiB/s | 18.94 MiB/s |
> > | deflate | 65536 | 452 MiB/s | 159 MiB/s | 13.02 MiB/s |
> > | deflate | 131072 | 452 MiB/s | 177 MiB/s | 11.44 MiB/s |
> > | deflate | 262144 | 466 MiB/s | 194 MiB/s | 10.60 MiB/s |
> >
> > Signed-off-by: Bo Liu <liubo03@inspur.com>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>
BTW, the commit message has been updated to v4 version to
fix some typos:
https://lore.kernel.org/r/20250521100326.2867828-1-hsiangkao@linux.alibaba.com
Thanks,
Gao Xiang
prev parent reply other threads:[~2025-05-22 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 9:49 Bo Liu
2025-05-22 9:52 ` Gao Xiang
2025-05-22 13:57 ` Gao Xiang [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=aC8tX4u/EFe8XsVP@debian \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.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®