From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, Dave Chinner <dchinner@redhat.com>
Subject: Re: [PATCH 1/4] xfs: reduce context switches for synchronous buffered I/O
Date: Mon, 24 Feb 2025 21:37:34 -0800 [thread overview]
Message-ID: <20250225053734.GA6242@frogsfrogsfrogs> (raw)
In-Reply-To: <20250224234903.402657-2-hch@lst.de>
On Mon, Feb 24, 2025 at 03:48:52PM -0800, Christoph Hellwig wrote:
> Currently all metadata I/O completions happen in the m_buf_workqueue
> workqueue. But for synchronous I/O (i.e. all buffer reads) there is no
> need for that, as there always is a called in process context that is
> waiting for the I/O. Factor out the guts of xfs_buf_ioend into a
> separate helper and call it from xfs_buf_iowait to avoid a double
> an extra context switch to the workqueue.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Dave Chinner <dchinner@redhat.com>
Looks good now,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_buf.c | 43 +++++++++++++++++++++++++++----------------
> 1 file changed, 27 insertions(+), 16 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index 15bb790359f8..dfc1849b3314 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
> @@ -1345,6 +1345,7 @@ xfs_buf_ioend_handle_error(
> resubmit:
> xfs_buf_ioerror(bp, 0);
> bp->b_flags |= (XBF_DONE | XBF_WRITE_FAIL);
> + reinit_completion(&bp->b_iowait);
> xfs_buf_submit(bp);
> return true;
> out_stale:
> @@ -1355,8 +1356,9 @@ xfs_buf_ioend_handle_error(
> return false;
> }
>
> -static void
> -xfs_buf_ioend(
> +/* returns false if the caller needs to resubmit the I/O, else true */
> +static bool
> +__xfs_buf_ioend(
> struct xfs_buf *bp)
> {
> trace_xfs_buf_iodone(bp, _RET_IP_);
> @@ -1376,7 +1378,7 @@ xfs_buf_ioend(
> }
>
> if (unlikely(bp->b_error) && xfs_buf_ioend_handle_error(bp))
> - return;
> + return false;
>
> /* clear the retry state */
> bp->b_last_error = 0;
> @@ -1397,7 +1399,15 @@ xfs_buf_ioend(
>
> bp->b_flags &= ~(XBF_READ | XBF_WRITE | XBF_READ_AHEAD |
> _XBF_LOGRECOVERY);
> + return true;
> +}
>
> +static void
> +xfs_buf_ioend(
> + struct xfs_buf *bp)
> +{
> + if (!__xfs_buf_ioend(bp))
> + return;
> if (bp->b_flags & XBF_ASYNC)
> xfs_buf_relse(bp);
> else
> @@ -1411,15 +1421,8 @@ xfs_buf_ioend_work(
> struct xfs_buf *bp =
> container_of(work, struct xfs_buf, b_ioend_work);
>
> - xfs_buf_ioend(bp);
> -}
> -
> -static void
> -xfs_buf_ioend_async(
> - struct xfs_buf *bp)
> -{
> - INIT_WORK(&bp->b_ioend_work, xfs_buf_ioend_work);
> - queue_work(bp->b_mount->m_buf_workqueue, &bp->b_ioend_work);
> + if (__xfs_buf_ioend(bp))
> + xfs_buf_relse(bp);
> }
>
> void
> @@ -1491,7 +1494,13 @@ xfs_buf_bio_end_io(
> XFS_TEST_ERROR(false, bp->b_mount, XFS_ERRTAG_BUF_IOERROR))
> xfs_buf_ioerror(bp, -EIO);
>
> - xfs_buf_ioend_async(bp);
> + if (bp->b_flags & XBF_ASYNC) {
> + INIT_WORK(&bp->b_ioend_work, xfs_buf_ioend_work);
> + queue_work(bp->b_mount->m_buf_workqueue, &bp->b_ioend_work);
> + } else {
> + complete(&bp->b_iowait);
> + }
> +
> bio_put(bio);
> }
>
> @@ -1568,9 +1577,11 @@ xfs_buf_iowait(
> {
> ASSERT(!(bp->b_flags & XBF_ASYNC));
>
> - trace_xfs_buf_iowait(bp, _RET_IP_);
> - wait_for_completion(&bp->b_iowait);
> - trace_xfs_buf_iowait_done(bp, _RET_IP_);
> + do {
> + trace_xfs_buf_iowait(bp, _RET_IP_);
> + wait_for_completion(&bp->b_iowait);
> + trace_xfs_buf_iowait_done(bp, _RET_IP_);
> + } while (!__xfs_buf_ioend(bp));
>
> return bp->b_error;
> }
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2025-02-25 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 23:48 buffer cache simplifications v3 Christoph Hellwig
2025-02-24 23:48 ` [PATCH 1/4] xfs: reduce context switches for synchronous buffered I/O Christoph Hellwig
2025-02-25 5:37 ` Darrick J. Wong [this message]
2025-02-24 23:48 ` [PATCH 2/4] xfs: decouple buffer readahead from the normal buffer read path Christoph Hellwig
2025-02-24 23:48 ` [PATCH 3/4] xfs: remove most in-flight buffer accounting Christoph Hellwig
2025-02-24 23:48 ` [PATCH 4/4] xfs: remove the XBF_STALE check from xfs_buf_rele_cached Christoph Hellwig
2025-02-26 10:01 ` buffer cache simplifications v3 Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 15:11 buffer cache simplifications v2 Christoph Hellwig
2025-02-24 15:11 ` [PATCH 1/4] xfs: reduce context switches for synchronous buffered I/O Christoph Hellwig
2025-02-24 19:13 ` Darrick J. Wong
2025-02-17 9:31 buffer cache simplifications Christoph Hellwig
2025-02-17 9:31 ` [PATCH 1/4] xfs: reduce context switches for synchronous buffered I/O Christoph Hellwig
2025-02-18 20:05 ` Darrick J. Wong
2025-02-19 5:32 ` 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=20250225053734.GA6242@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--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