From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3 1/2] xfs: refactor buffer submission into a common helper
Date: Fri, 15 Jun 2018 04:24:14 -0700 [thread overview]
Message-ID: <20180615112414.GA3230@infradead.org> (raw)
In-Reply-To: <20180614134307.26868-1-bfoster@redhat.com>
On Thu, Jun 14, 2018 at 09:43:07AM -0400, Brian Foster wrote:
> Sync and async buffer submission both do generally similar things
> with a couple odd exceptions. Refactor the core buffer submission
> code into a common helper to isolate buffer submission from
> completion handling of synchronous buffer I/O.
>
> This patch does not change behavior. It is a step towards support
> for using synchronous buffer I/O via synchronous delwri queue
> submission.
>
> Designed-by: Dave Chinner <dchinner@redhat.com>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>
> v3:
> - Leave tracepoint in __xfs_buf_submit and kill
> trace_xfs_buf_submit_wait().
>
> fs/xfs/xfs_buf.c | 85 ++++++++++++++++++++--------------------------
> fs/xfs/xfs_trace.h | 1 -
> 2 files changed, 37 insertions(+), 49 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index e9c058e3761c..7b0f7c79cd62 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
> @@ -1458,22 +1458,20 @@ _xfs_buf_ioapply(
> * a call to this function unless the caller holds an additional reference
> * itself.
> */
> -void
> -xfs_buf_submit(
> +static int
> +__xfs_buf_submit(
> struct xfs_buf *bp)
> {
> trace_xfs_buf_submit(bp, _RET_IP_);
>
> ASSERT(!(bp->b_flags & _XBF_DELWRI_Q));
> - ASSERT(bp->b_flags & XBF_ASYNC);
>
> /* on shutdown we stale and complete the buffer immediately */
> if (XFS_FORCED_SHUTDOWN(bp->b_target->bt_mount)) {
> xfs_buf_ioerror(bp, -EIO);
> bp->b_flags &= ~XBF_DONE;
> xfs_buf_stale(bp);
> - xfs_buf_ioend(bp);
> - return;
> + return -EIO;
> }
>
> if (bp->b_flags & XBF_WRITE)
> @@ -1482,23 +1480,14 @@ xfs_buf_submit(
> /* clear the internal error state to avoid spurious errors */
> bp->b_io_error = 0;
>
> - /*
> - * The caller's reference is released during I/O completion.
> - * This occurs some time after the last b_io_remaining reference is
> - * released, so after we drop our Io reference we have to have some
> - * other reference to ensure the buffer doesn't go away from underneath
> - * us. Take a direct reference to ensure we have safe access to the
> - * buffer until we are finished with it.
> - */
> - xfs_buf_hold(bp);
> -
> /*
> * Set the count to 1 initially, this will stop an I/O completion
> * callout which happens before we have started all the I/O from calling
> * xfs_buf_ioend too early.
> */
> atomic_set(&bp->b_io_remaining, 1);
> - xfs_buf_ioacct_inc(bp);
> + if (bp->b_flags & XBF_ASYNC)
> + xfs_buf_ioacct_inc(bp);
> _xfs_buf_ioapply(bp);
>
> /*
> @@ -1507,14 +1496,39 @@ xfs_buf_submit(
> * that we don't return to the caller with completion still pending.
> */
> if (atomic_dec_and_test(&bp->b_io_remaining) == 1) {
> - if (bp->b_error)
> + if (bp->b_error || !(bp->b_flags & XBF_ASYNC))
> xfs_buf_ioend(bp);
> else
> xfs_buf_ioend_async(bp);
> }
>
> - xfs_buf_rele(bp);
> + return 0;
> +}
> +
> +void
> +xfs_buf_submit(
> + struct xfs_buf *bp)
> +{
> + int error;
> +
> + ASSERT(bp->b_flags & XBF_ASYNC);
> +
> + /*
> + * The caller's reference is released during I/O completion.
> + * This occurs some time after the last b_io_remaining reference is
> + * released, so after we drop our Io reference we have to have some
> + * other reference to ensure the buffer doesn't go away from underneath
> + * us. Take a direct reference to ensure we have safe access to the
> + * buffer until we are finished with it.
> + */
> + xfs_buf_hold(bp);
> +
> + error = __xfs_buf_submit(bp);
> + if (error)
> + xfs_buf_ioend(bp);
> +
It seems like we could simple throw in a:
if (!(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_);
error = bp->b_error;;
}
here and get ret rid of the separate xfs_buf_submit_wait function
entirely. Or even factor the above out into a nice little helper.
Otherwise this looks fine to me:
Signed-off-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-06-15 11:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 11:05 [PATCH v2 0/2] xfs: fix buffer delwri queue state race Brian Foster
2018-06-13 11:05 ` [PATCH v2 1/2] xfs: refactor buffer submission into a common helper Brian Foster
2018-06-14 13:43 ` [PATCH v3 " Brian Foster
2018-06-15 11:24 ` Christoph Hellwig [this message]
2018-06-15 11:53 ` Brian Foster
2018-06-13 11:05 ` [PATCH v2 2/2] xfs: use sync buffer I/O for sync delwri queue submission Brian Foster
2018-06-13 22:08 ` Dave Chinner
2018-06-13 23:29 ` Brian Foster
2018-06-13 23:37 ` Dave Chinner
2018-06-15 11:28 ` Christoph Hellwig
2018-06-15 11:53 ` Brian Foster
2018-06-15 12:16 ` Christoph Hellwig
2018-06-15 12:39 ` Brian Foster
2018-06-15 16:31 ` Darrick J. Wong
2018-06-15 17:43 ` Brian Foster
2018-06-18 11:21 ` Christoph Hellwig
2018-06-18 11:47 ` Brian Foster
-- strict thread matches above, loose matches on Subject: below --
2018-06-15 18:05 [PATCH v3 0/2] xfs: fix buffer delwri queue state race Brian Foster
2018-06-15 18:05 ` [PATCH v3 1/2] xfs: refactor buffer submission into a common helper Brian Foster
2018-06-19 5:21 ` Darrick J. Wong
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=20180615112414.GA3230@infradead.org \
--to=hch@infradead.org \
--cc=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 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).