All of lore.kernel.org
 help / color / mirror / Atom feed
From: JeffleXu <jefflexu@linux.alibaba.com>
To: axboe@kernel.dk, hch@infradead.org, ming.lei@redhat.com
Cc: linux-block@vger.kernel.org, io-uring@vger.kernel.org,
	joseph.qi@linux.alibaba.com
Subject: Re: [PATCH v4 1/2] block: disable iopoll for split bio
Date: Thu, 19 Nov 2020 11:06:08 +0800	[thread overview]
Message-ID: <e0d59ea2-3c30-9edb-4cbb-f63703fdf0f1@linux.alibaba.com> (raw)
In-Reply-To: <20201117075625.46118-2-jefflexu@linux.alibaba.com>

Hi Jens,

Would you mind giving a glance at this, at least patch 1?


Patch 1 could fix the potential deadlock may be triggered by sync io polling

in direct IO routine.


Actually this patch could alleviate another potential hang in io_uring. The

returned cookie of submit_bio() is actually the cookie of the last split bio

if splitting happened. If the returned cookie is BLK_QC_T_NONE ( the

last split bio get merged into another request, or queue depth exhausted

and REQ_NOWAIT set by io_uring), then iocb->ki_cookie is BLK_QC_T_NONE.


If there's only this one IO (though split to several bios) in the 
polling hw queue,

then io_do_iopoll() will get stuck in indefinite calling of blk_poll(), 
while blk_poll()

will return 0 immediately because of BLK_QC_T_NONE, without reaping any

former completed requests.


This hang rarly happened, maybe because as long as there's other IO, polling

of these other IOs will help reap completed requests of the stuck IO 
described

above.


Of course we could refactor the problematic logic of returning cookie in 
submit_bio(),

But this patch 1 could also fix this issue. Besides this patch 1 is also 
needed to fix

the potential deadlock triggered by sync io polling described above.


Thanks,

Jeffle



On 11/17/20 3:56 PM, Jeffle Xu wrote:
> iopoll is initially for small size, latency sensitive IO. It doesn't
> work well for big IO, especially when it needs to be split to multiple
> bios. In this case, the returned cookie of __submit_bio_noacct_mq() is
> indeed the cookie of the last split bio. The completion of *this* last
> split bio done by iopoll doesn't mean the whole original bio has
> completed. Callers of iopoll still need to wait for completion of other
> split bios.
>
> Besides bio splitting may cause more trouble for iopoll which isn't
> supposed to be used in case of big IO.
>
> iopoll for split bio may cause potential race if CPU migration happens
> during bio submission. Since the returned cookie is that of the last
> split bio, polling on the corresponding hardware queue doesn't help
> complete other split bios, if these split bios are enqueued into
> different hardware queues. Since interrupts are disabled for polling
> queues, the completion of these other split bios depends on timeout
> mechanism, thus causing a potential hang.
>
> iopoll for split bio may also cause hang for sync polling. Currently
> both the blkdev and iomap-based fs (ext4/xfs, etc) support sync polling
> in direct IO routine. These routines will submit bio without REQ_NOWAIT
> flag set, and then start sync polling in current process context. The
> process may hang in blk_mq_get_tag() if the submitted bio has to be
> split into multiple bios and can rapidly exhaust the queue depth. The
> process are waiting for the completion of the previously allocated
> requests, which should be reaped by the following polling, and thus
> causing a deadlock.
>
> To avoid these subtle trouble described above, just disable iopoll for
> split bio.
>
> Suggested-by: Ming Lei <ming.lei@redhat.com>
> Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
> ---
>   block/blk-merge.c | 7 +++++++
>   block/blk-mq.c    | 6 ++++--
>   2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index bcf5e4580603..53ad781917a2 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -279,6 +279,13 @@ static struct bio *blk_bio_segment_split(struct request_queue *q,
>   	return NULL;
>   split:
>   	*segs = nsegs;
> +
> +	/*
> +	 * bio splitting may cause subtle trouble such as hang when doing iopoll,
> +	 * not to mention iopoll isn't supposed to be used in case of big IO.
> +	 */
> +	bio->bi_opf &= ~REQ_HIPRI;
> +
>   	return bio_split(bio, sectors, GFP_NOIO, bs);
>   }
>   
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 55bcee5dc032..6d10652a7ed0 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -3853,11 +3853,13 @@ int blk_poll(struct request_queue *q, blk_qc_t cookie, bool spin)
>   	    !test_bit(QUEUE_FLAG_POLL, &q->queue_flags))
>   		return 0;
>   
> +	hctx = q->queue_hw_ctx[blk_qc_t_to_queue_num(cookie)];
> +	if (hctx->type != HCTX_TYPE_POLL)
> +		return 0;
> +
>   	if (current->plug)
>   		blk_flush_plug_list(current->plug, false);
>   
> -	hctx = q->queue_hw_ctx[blk_qc_t_to_queue_num(cookie)];
> -
>   	/*
>   	 * If we sleep, have the caller restart the poll loop to reset
>   	 * the state. Like for the other success return cases, the

-- 
Thanks,
Jeffle


  reply	other threads:[~2020-11-19  3:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  7:56 [PATCH v4 0/2] block, iomap: disable iopoll for split bio Jeffle Xu
2020-11-17  7:56 ` [PATCH v4 1/2] block: " Jeffle Xu
2020-11-19  3:06   ` JeffleXu [this message]
2020-11-19 17:52   ` Christoph Hellwig
2020-11-20  9:22     ` JeffleXu
2020-11-17  7:56 ` [PATCH v4 2/2] block,iomap: disable iopoll when split needed Jeffle Xu
2020-11-17 17:37   ` Darrick J. Wong
2020-11-18  1:56     ` JeffleXu
2020-11-19 17:55   ` Christoph Hellwig
2020-11-20 10:06     ` JeffleXu
2020-11-20 10:09       ` Fwd: " JeffleXu
2020-11-24 11:25       ` Christoph Hellwig
2020-11-25  7:03         ` JeffleXu
2020-11-17 12:51 ` [PATCH v4 0/2] block, iomap: disable iopoll for split bio JeffleXu
2020-11-18  9:50   ` JeffleXu

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=e0d59ea2-3c30-9edb-4cbb-f63703fdf0f1@linux.alibaba.com \
    --to=jefflexu@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=io-uring@vger.kernel.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    /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.