From: Jens Axboe <axboe@kernel.dk>
To: cem@kernel.org, djwong@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCHSET v2 0/2] Add XFS support for RWF_DONTCACHE
Date: Wed, 26 Feb 2025 10:30:05 -0700 [thread overview]
Message-ID: <ba718fc2-08ba-4d7e-98f9-47f3f52c13a8@kernel.dk> (raw)
In-Reply-To: <20250204184047.356762-1-axboe@kernel.dk>
On 2/4/25 11:39 AM, Jens Axboe wrote:
> Hi,
>
> Now that the main bits are in mainline, here are the XFS patches for
> adding RWF_DONTCACHE support. It's pretty trivial - patch 1 adds the
> basic iomap flag and check, and patch 2 flags FOP_DONTCACHE support
> in the file_operations struct. Could be folded into a single patch
> at this point, I'll leave that up to you guys what you prefer.
>
> Patches are aginst 6.14-rc1.
>
> Since v1:
> - Remove stale commit message paragraph
> - Add comments for iomap flag from Darrick
Is this slated for 6.15? I don't see it in the tree yet, but I also
don't see a lot of other things in there. Would be a shame to miss the
next release on this front.
--
Jens Axboe
next prev parent reply other threads:[~2025-02-26 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 18:39 [PATCHSET v2 0/2] Add XFS support for RWF_DONTCACHE Jens Axboe
2025-02-04 18:39 ` [PATCH 1/2] iomap: make buffered writes work with RWF_DONTCACHE Jens Axboe
2025-02-20 6:06 ` Christoph Hellwig
2025-02-27 9:51 ` Carlos Maiolino
2025-02-27 10:30 ` Christian Brauner
2025-02-27 10:57 ` Carlos Maiolino
2025-02-27 15:14 ` Christoph Hellwig
2025-02-28 10:38 ` Christian Brauner
2025-03-03 13:07 ` John Garry
2025-03-12 20:40 ` Chaitanya Kulkarni
2025-02-04 18:40 ` [PATCH 2/2] xfs: flag as supporting FOP_DONTCACHE Jens Axboe
2025-02-04 18:59 ` Darrick J. Wong
2025-02-20 6:07 ` Christoph Hellwig
2025-03-12 20:42 ` Chaitanya Kulkarni
2025-02-19 17:12 ` [PATCHSET v2 0/2] Add XFS support for RWF_DONTCACHE Jens Axboe
2025-02-26 17:30 ` Jens Axboe [this message]
2025-02-27 9:25 ` Carlos Maiolino
2025-02-27 15:05 ` Jens Axboe
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=ba718fc2-08ba-4d7e-98f9-47f3f52c13a8@kernel.dk \
--to=axboe@kernel.dk \
--cc=cem@kernel.org \
--cc=djwong@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.