From: Christian Brauner <brauner@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Hans Holmberg <Hans.Holmberg@wdc.com>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
"Darrick J . Wong" <djwong@kernel.org>, hch <hch@lst.de>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] fs: add an enum for number of life time hints
Date: Fri, 5 Sep 2025 16:03:51 +0200 [thread overview]
Message-ID: <20250905-posaunen-lenken-e81db0559def@brauner> (raw)
In-Reply-To: <gzj54cob33ecyfdabfbvci7nj7gl5sc2cbujpkg6qax7vgoph2@3ubnb4d2dfim>
On Fri, Sep 05, 2025 at 10:17:51AM +0200, Carlos Maiolino wrote:
> On Mon, Sep 01, 2025 at 10:52:04AM +0000, Hans Holmberg wrote:
> > Add WRITE_LIFE_HINT_NR into the rw_hint enum to define the number of
> > values write life time hints can be set to. This is useful for e.g.
> > file systems which may want to map these values to allocation groups.
> >
> > Signed-off-by: Hans Holmberg <hans.holmberg@wdc.com>
>
> Cc'ing Chris Brauner here, as I think he is who will be picking this up.
This is so trivial, just take it through xfs, please.
next prev parent reply other threads:[~2025-09-05 14:03 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 [this message]
2025-09-16 10:30 ` Carlos Maiolino
2025-09-01 10:52 ` [PATCH 2/3] xfs: refactor hint based zone allocation Hans Holmberg
2025-09-02 5:41 ` hch
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-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=20250905-posaunen-lenken-e81db0559def@brauner \
--to=brauner@kernel.org \
--cc=Hans.Holmberg@wdc.com \
--cc=cem@kernel.org \
--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