From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v4 0/6] xfs: properly invalidate cached writeback mapping
Date: Fri, 1 Feb 2019 09:32:50 -0500 [thread overview]
Message-ID: <20190201143256.43232-1-bfoster@redhat.com> (raw)
Hi all,
This is a minor update of this series to fold in some changes from
Christoph's follow on series to rework the delalloc conversion code. The
changes apply to patches 5 and 6 and rename/rework the delalloc helper.
The subsequent series will fill in a real implementation for the wrapper
and further clean up the writeback code.
Brian
v4:
- Fold in Christoph's interface changes from the delalloc conversion
rework series (patches 5-6).
v3: https://marc.info/?l=linux-xfs&m=154826889919747&w=2
- Move comment in xfs_imap_valid().
- Replace lookup+trim in xfs_iomap_write_allocate() with
xfs_bmapi_delalloc() wrapper mechanism.
v2: https://marc.info/?l=linux-xfs&m=154775280823464&w=2
- Refactor validation logic into xfs_imap_valid() helper.
- Revalidate seqno after the lock cycle in xfs_map_blocks().
- Update *seq in xfs_iomap_write_allocate() regardless of fork type.
- Add patch 5 for seqno revalidation on xfs_iomap_write_allocate() lock
cycles.
v1: https://marc.info/?l=linux-xfs&m=154721212321112&w=2
Brian Foster (6):
xfs: eof trim writeback mapping as soon as it is cached
xfs: update fork seq counter on data fork changes
xfs: validate writeback mapping using data fork seq counter
xfs: remove superfluous writeback mapping eof trimming
xfs: create delalloc bmapi wrapper for full extent allocation
xfs: use the latest extent at writeback delalloc conversion time
fs/xfs/libxfs/xfs_bmap.c | 68 ++++++++++---
fs/xfs/libxfs/xfs_bmap.h | 3 +-
fs/xfs/libxfs/xfs_iext_tree.c | 13 ++-
fs/xfs/libxfs/xfs_inode_fork.h | 2 +-
fs/xfs/xfs_aops.c | 71 +++++++++-----
fs/xfs/xfs_iomap.c | 171 +++++++++++----------------------
6 files changed, 165 insertions(+), 163 deletions(-)
--
2.17.2
next reply other threads:[~2019-02-01 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 14:32 Brian Foster [this message]
2019-02-01 14:32 ` [PATCH v4 1/6] xfs: eof trim writeback mapping as soon as it is cached Brian Foster
2019-02-01 14:32 ` [PATCH v4 2/6] xfs: update fork seq counter on data fork changes Brian Foster
2019-02-01 14:32 ` [PATCH v4 3/6] xfs: validate writeback mapping using data fork seq counter Brian Foster
2019-02-01 14:32 ` [PATCH v4 4/6] xfs: remove superfluous writeback mapping eof trimming Brian Foster
2019-02-01 14:32 ` [PATCH v4 5/6] xfs: create delalloc bmapi wrapper for full extent allocation Brian Foster
2019-02-02 16:08 ` Christoph Hellwig
2019-02-01 14:32 ` [PATCH v4 6/6] xfs: use the latest extent at writeback delalloc conversion time Brian Foster
2019-02-02 16:09 ` Christoph Hellwig
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=20190201143256.43232-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--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.