From: hch <hch@lst.de>
To: Hans Holmberg <Hans.Holmberg@wdc.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Carlos Maiolino <cem@kernel.org>,
Dave Chinner <david@fromorbit.com>,
"Darrick J . Wong" <djwong@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] xfs: adjust the hint based zone allocation policy
Date: Tue, 2 Sep 2025 07:42:01 +0200 [thread overview]
Message-ID: <20250902054201.GC11431@lst.de> (raw)
In-Reply-To: <20250901105128.14987-4-hans.holmberg@wdc.com>
On Mon, Sep 01, 2025 at 10:52:05AM +0000, Hans Holmberg wrote:
> As we really can't make any general assumptions about files that don't
> have any life time hint set or are set to "NONE", adjust the allocation
> policy to avoid co-locating data from those files with files with a set
> life time.
>
> Signed-off-by: Hans Holmberg <hans.holmberg@wdc.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-09-02 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 10:52 [PATCH 0/3] xfs: hint based zone allocation improvements 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 [this message]
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 ` [PATCH 0/3] xfs: hint based zone allocation improvements Carlos Maiolino
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=20250902054201.GC11431@lst.de \
--to=hch@lst.de \
--cc=Hans.Holmberg@wdc.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.