From: Brian Foster <bfoster@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org,
josef@toxicpanda.com, david@fromorbit.com
Subject: [PATCH v3 0/2] iomap: flush dirty cache over unwritten mappings on zero range
Date: Fri, 30 Aug 2024 10:56:32 -0400 [thread overview]
Message-ID: <20240830145634.138439-1-bfoster@redhat.com> (raw)
Hi all,
Here's v3 of the iomap zero range flush fixes. No real changes here
other than comment updates to better explain the flush and stale logic.
The latest version of corresponding test support is posted here [1].
Thoughts, reviews, flames appreciated.
v3:
- Rework comment(s) in patch 2 to explain marking the mapping stale.
- Added R-b tags.
v2: https://lore.kernel.org/linux-fsdevel/20240828181912.41517-1-bfoster@redhat.com/
- Update comment in patch 2 to explain hole case.
v1: https://lore.kernel.org/linux-fsdevel/20240822145910.188974-1-bfoster@redhat.com/
- Alternative approach, flush instead of revalidate.
rfc: https://lore.kernel.org/linux-fsdevel/20240718130212.23905-1-bfoster@redhat.com/
Brian Foster (2):
iomap: fix handling of dirty folios over unwritten extents
iomap: make zero range flush conditional on unwritten mappings
fs/iomap/buffered-io.c | 63 +++++++++++++++++++++++++++++++++++++++---
fs/xfs/xfs_iops.c | 10 -------
2 files changed, 59 insertions(+), 14 deletions(-)
--
2.45.0
next reply other threads:[~2024-08-30 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 14:56 Brian Foster [this message]
2024-08-30 14:56 ` [PATCH v3 1/2] iomap: fix handling of dirty folios over unwritten extents Brian Foster
2024-08-30 14:56 ` [PATCH v3 2/2] iomap: make zero range flush conditional on unwritten mappings Brian Foster
2024-09-03 7:59 ` [PATCH v3 0/2] iomap: flush dirty cache over unwritten mappings on zero range Christian Brauner
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=20240830145634.138439-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).