From: Chandan Babu R <chandanbabu@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Wang Jianchao <jianchwa@outlook.com>,
Chandan Babu R <chandanrlinux@gmail.com>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] xfs: use roundup_pow_of_two instead of ffs during xlog_find_tail
Date: Tue, 19 Sep 2023 12:04:44 +0530 [thread overview]
Message-ID: <874jjqk6t2.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20230919032138.GC348037@frogsfrogsfrogs>
On Mon, Sep 18, 2023 at 08:21:38 PM -0700, Darrick J. Wong wrote:
> On Tue, Sep 19, 2023 at 10:06:56AM +0800, Wang Jianchao wrote:
>> Ping ? Do I need other update on this patch ?
>
> Nope, I think this is ok...
>
>> Thanks
>> Jianchao
>>
>> On 2023/9/13 09:38, Wang Jianchao wrote:
>> >
>> > In our production environment, we find that mounting a 500M /boot
>> > which is umount cleanly needs ~6s. One cause is that ffs() is
>> > used by xlog_write_log_records() to decide the buffer size. It
>> > can cause a lot of small IO easily when xlog_clear_stale_blocks()
>> > needs to wrap around the end of log area and log head block is
>> > not power of two. Things are similar in xlog_find_verify_cycle().
>> >
>> > The code is able to handed bigger buffer very well, we can use
>> > roundup_pow_of_two() to replace ffs() directly to avoid small
>> > and sychronous IOs.
>> >
>> > Reviewed-by: Dave Chinner <dchinner@redhat.com>
>> > Signed-off-by: Wang Jianchao <wangjc136@midea.com>
>
> ...so let's see if the release manager will take this patch.
>
> Chandan? Could you pull in the various one-off patches floating around
> on the list that have passed review? ;)
I had picked this patch along with others sometime last week.
I have pushed the new set of commits to official xfs-linux git repository and
sent the announcement mail around 30 mins ago.
>
> Reviewed-by: Darrick J. Wong <djwong@kernel.org>
>
> PS: If you'd like to send a pull request to push things along, please do
>
--
Chandan
prev parent reply other threads:[~2023-09-19 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <63b3742c-0efe-c096-c737-a0e0419480bd@outlook.com>
2023-09-12 7:20 ` [PATCH V2] " Wang Jianchao
2023-09-12 22:44 ` Dave Chinner
2023-09-13 1:33 ` Wang Jianchao
[not found] ` <59dd15dd-5b35-871d-6d3a-ec779975b089@outlook.com>
2023-09-13 1:38 ` [PATCH V3] " Wang Jianchao
[not found] ` <0a72f462-8b8e-4dec-6ce4-f52e33423957@outlook.com>
2023-09-19 2:06 ` Wang Jianchao
2023-09-19 3:21 ` Darrick J. Wong
2023-09-19 6:34 ` Chandan Babu R [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=874jjqk6t2.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=chandanrlinux@gmail.com \
--cc=djwong@kernel.org \
--cc=jianchwa@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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®