From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Salman Qazi <sqazi@google.com>,
Jesse Barnes <jsbarnes@google.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH V2] block: Prevent hung_check firing during long sync IO
Date: Wed, 18 Mar 2020 08:48:49 -0600 [thread overview]
Message-ID: <3588c35d-3d16-7f5c-03fe-4a469a887342@kernel.dk> (raw)
In-Reply-To: <20200318034336.6212-1-ming.lei@redhat.com>
On 3/17/20 9:43 PM, Ming Lei wrote:
> submit_bio_wait() can be called from ioctl(BLKSECDISCARD), which
> may take long time to complete, as Salman mentioned, 4K BLKSECDISCARD
> takes up to 100 second on some devices. Also any block I/O operation
> that occurs after the BLKSECDISCARD is submitted will also potentially
> be affected by the hung task timeouts.
>
> Another report is that task hang can be observed when running mkfs
> over raid10 which takes a small max discard sectors limit because
> of chunk size.
>
> So prevent hung_check from firing by taking same approach used
> in blk_execute_rq(), and the wake-up interval is set as half the
> hung_check timer period, which keeps overhead low enough.
Applied, thanks.
We have two of these similar constructs now in block alone, I wonder
if there are others in other sub-systems. Might make sense to make
this a generic helper at some point.
--
Jens Axboe
prev parent reply other threads:[~2020-03-18 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 3:43 [PATCH V2] block: Prevent hung_check firing during long sync IO Ming Lei
2020-03-18 10:55 ` Guoqing Jiang
2020-03-18 11:07 ` Ming Lei
2020-03-18 14:48 ` Jens Axboe [this message]
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=3588c35d-3d16-7f5c-03fe-4a469a887342@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=jsbarnes@google.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=sqazi@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox