From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org, Hans Holmberg <Hans.Holmberg@wdc.com>
Cc: Dave Chinner <david@fromorbit.com>,
"Darrick J . Wong" <djwong@kernel.org>, hch <hch@lst.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] xfs: hint based zone allocation improvements
Date: Tue, 16 Sep 2025 13:34:47 +0200 [thread overview]
Message-ID: <175802248724.997282.6225952797513053259.b4-ty@kernel.org> (raw)
In-Reply-To: <20250901105128.14987-1-hans.holmberg@wdc.com>
On Mon, 01 Sep 2025 10:52:03 +0000, Hans Holmberg wrote:
> This series makes the zone allocation policy a bit easier to
> understand and adjusts the policy for unset and "none" rw hints,
> avoiding mixing these with files with file data with set values.
>
> The first patch adds an enum for the number of hints available,
> the second introduces allocation matrix without changing the policy,
> and rhe third adjusts the allocation policy.
>
> [...]
Applied to for-next, thanks!
[1/3] fs: add an enum for number of life time hints
commit: 94deac977fbd0246c971b4f1d17a6385f5e0b1a4
[2/3] xfs: refactor hint based zone allocation
commit: 0301dae732a5402a68fdb8d8461b97da6b9bccc6
[3/3] xfs: adjust the hint based zone allocation policy
commit: 8e2cdd8e18ff5073ad76ab2220910001eae39398
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2025-09-16 11:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 10:52 Hans Holmberg
2025-09-01 10:52 ` [PATCH 1/3] fs: add an enum for number of life time hints Hans Holmberg
2025-09-02 5:41 ` hch
2025-09-02 8:47 ` Hans Holmberg
2025-09-02 16:12 ` Bart Van Assche
2025-09-05 8:17 ` Carlos Maiolino
2025-09-05 14:03 ` Christian Brauner
2025-09-16 10:30 ` Carlos Maiolino
2025-09-01 10:52 ` [PATCH 3/3] xfs: adjust the hint based zone allocation policy Hans Holmberg
2025-09-02 5:42 ` hch
2025-09-01 10:52 ` [PATCH 2/3] xfs: refactor hint based zone allocation Hans Holmberg
2025-09-02 5:41 ` hch
2025-09-16 11:34 ` Carlos Maiolino [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=175802248724.997282.6225952797513053259.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=Hans.Holmberg@wdc.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--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®