From: Christoph Hellwig <hch@lst.de>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>, linux-xfs@vger.kernel.org
Subject: clean up I/O path inode locking helpers and the page fault handler v2
Date: Sun, 23 Jun 2024 07:44:25 +0200 [thread overview]
Message-ID: <20240623054500.870845-1-hch@lst.de> (raw)
Hi all,
a while ago I started wondering about some of the I/O path locking,
and ended up wading through the various helpers. This series refactors
them an improves comments to help understanding. To get there I also
took a hard look at the page fault handler and ended up refactoring it
as well.
Changes since v1:
- rename xfs_dax_fault to xfs_dax_read_fault
Diffstat:
xfs_file.c | 139 ++++++++++++++++++++++++++++++++----------------------------
xfs_iomap.c | 71 ++++++++++++++----------------
2 files changed, 109 insertions(+), 101 deletions(-)
next reply other threads:[~2024-06-23 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 5:44 Christoph Hellwig [this message]
2024-06-23 5:44 ` [PATCH 1/6] xfs: move the dio write relocking out of xfs_ilock_for_iomap Christoph Hellwig
2024-06-23 5:44 ` [PATCH 2/6] xfs: cleanup xfs_ilock_iocb_for_write Christoph Hellwig
2024-06-23 5:44 ` [PATCH 3/6] xfs: simplify xfs_dax_fault Christoph Hellwig
2024-06-23 5:44 ` [PATCH 4/6] xfs: refactor __xfs_filemap_fault Christoph Hellwig
2024-06-23 5:44 ` [PATCH 5/6] xfs: always take XFS_MMAPLOCK shared in xfs_dax_read_fault Christoph Hellwig
2024-06-23 5:44 ` [PATCH 6/6] xfs: fold xfs_ilock_for_write_fault into xfs_write_fault 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=20240623054500.870845-1-hch@lst.de \
--to=hch@lst.de \
--cc=chandan.babu@oracle.com \
--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