From: Qu Wenruo <wqu@suse.com>
To: dsterba@suse.cz, Zaslonko Mikhail <zaslonko@linux.ibm.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org, linux-s390@vger.kernel.org,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH] btrfs: zlib: do not do unnecessary page copying for compression
Date: Wed, 29 May 2024 07:32:58 +0930 [thread overview]
Message-ID: <4c012b7d-52f9-469d-b272-bd93f3e73854@suse.com> (raw)
In-Reply-To: <20240528214350.GI8631@twin.jikos.cz>
在 2024/5/29 07:13, David Sterba 写道:
> On Tue, May 28, 2024 at 12:44:19PM +0200, Zaslonko Mikhail wrote:
>>> But I'm still wondering if we do not go 4 pages as buffer, how much
>>> performance penalty would there be?
>>>
>>> One of the objective is to prepare for the incoming sector perfect
>>> subpage compression support, thus I'm re-checking the existing
>>> compression code, preparing to change them to be subpage compatible.
>>>
>>> If we can simplify the behavior without too large performance penalty,
>>> can we consider just using one single page as buffer?
>>
>> Based on my earlier estimates, bigger buffer provided up to 60% performance for inflate and up to 30% for
>> deflate on s390 with dfltcc support.
>> I don't think giving it away for simplification would be a good idea.
>
> 60% and 30% sound like significant gain, I agree this takes precedence
> over code simplification. Eventually the s390 optimized case can be
> moved to a separate function if the conditions are satisfied so it's not
> mixed with the page-by-page code.
Thanks a lot for the numbers, the number is indeed impressive.
I'll definitely leave the larger buffer support untouched.
And thankfully since S390 only supports 4K page size, we won't need to
bother too much for that routine.
Thanks,
Qu
prev parent reply other threads:[~2024-05-28 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 9:24 [PATCH] btrfs: zlib: do not do unnecessary page copying for compression Qu Wenruo
2024-05-27 16:25 ` Zaslonko Mikhail
2024-05-27 22:09 ` Qu Wenruo
2024-05-28 10:44 ` Zaslonko Mikhail
2024-05-28 21:43 ` David Sterba
2024-05-28 22:02 ` Qu Wenruo [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=4c012b7d-52f9-469d-b272-bd93f3e73854@suse.com \
--to=wqu@suse.com \
--cc=dsterba@suse.cz \
--cc=gor@linux.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=zaslonko@linux.ibm.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