From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>
Cc: Hans Holmberg <hans.holmberg@wdc.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/4] xfs: refactor xfs_mount_zones
Date: Tue, 31 Mar 2026 18:21:50 +0900 [thread overview]
Message-ID: <ca081b37-4913-4a71-b6c8-d8e6c42a2147@kernel.org> (raw)
In-Reply-To: <20260330054111.3855818-2-hch@lst.de>
On 3/30/26 14:40, Christoph Hellwig wrote:
> xfs_mount_zones has grown a bit too big and unorganized. Split the
> zone reporting loop into a separate helper, hiding the rtg variable
> there. Print the mount message last, and also keep the VFS writeback
> chunk size last instead of in the middle of the logic to calculate
> the free/available blocks.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-03-31 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 5:40 fix handling of too many open zones at mount time Christoph Hellwig
2026-03-30 5:40 ` [PATCH 1/4] xfs: refactor xfs_mount_zones Christoph Hellwig
2026-03-31 7:12 ` Hans Holmberg
2026-03-31 9:21 ` Damien Le Moal [this message]
2026-03-30 5:40 ` [PATCH 2/4] xfs: handle too many open zones when mounting Christoph Hellwig
2026-03-31 7:34 ` Hans Holmberg
2026-03-31 9:30 ` Damien Le Moal
2026-03-30 5:40 ` [PATCH 3/4] xfs: expose the number of open zones in sysfs Christoph Hellwig
2026-03-31 7:39 ` Hans Holmberg
2026-03-31 9:35 ` Damien Le Moal
2026-03-30 5:41 ` [PATCH 4/4] xfs: untangle the open zones reporting in mountinfo Christoph Hellwig
2026-03-30 5:47 ` Christoph Hellwig
2026-03-30 9:55 ` Niklas Cassel
2026-03-30 13:10 ` Christoph Hellwig
2026-03-30 13:23 ` Carlos Maiolino
2026-03-31 7:41 ` Hans Holmberg
2026-03-31 9:36 ` Damien Le Moal
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=ca081b37-4913-4a71-b6c8-d8e6c42a2147@kernel.org \
--to=dlemoal@kernel.org \
--cc=cem@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--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