From: John Garry <john.g.garry@oracle.com>
To: Jens Axboe <axboe@kernel.dk>, cem@kernel.org, djwong@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] iomap: make buffered writes work with RWF_DONTCACHE
Date: Mon, 3 Mar 2025 13:07:02 +0000 [thread overview]
Message-ID: <d01de90f-eecd-4dcb-b1e1-e778bf9fc833@oracle.com> (raw)
In-Reply-To: <20250204184047.356762-2-axboe@kernel.dk>
On 04/02/2025 18:39, Jens Axboe wrote:
> --- a/include/linux/iomap.h
> +++ b/include/linux/iomap.h
> @@ -183,6 +183,7 @@ struct iomap_folio_ops {
> #define IOMAP_DAX 0
> #endif /* CONFIG_FS_DAX */
> #define IOMAP_ATOMIC (1 << 9)
> +#define IOMAP_DONTCACHE (1 << 10)
JFYI, IOMAP_FLAGS_STRINGS might need to be updated for this, but not
adding it may be intentional. I did not see anyone mention this in the
reviews.
Thanks,
John
next prev parent reply other threads:[~2025-03-03 13:07 UTC|newest]
Thread overview: 21+ 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 [this message]
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
2025-02-27 9:25 ` Carlos Maiolino
2025-02-27 15:05 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 16:32 [PATCHSET " Jens Axboe
2025-02-03 16:32 ` [PATCH 1/2] iomap: make buffered writes work with RWF_DONTCACHE Jens Axboe
2025-02-03 17:19 ` Darrick J. Wong
2025-02-03 18:26 ` 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=d01de90f-eecd-4dcb-b1e1-e778bf9fc833@oracle.com \
--to=john.g.garry@oracle.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox