linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Naohiro Aota <naohiro.aota@wdc.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	Niklas Cassel <Niklas.Cassel@wdc.com>
Subject: Re: [PATCH v2] block: schedule queue restart after BLK_STS_ZONE_RESOURCE
Date: Tue, 26 Oct 2021 16:00:56 -0600	[thread overview]
Message-ID: <163528565626.259196.4840508461738349119.b4-ty@kernel.dk> (raw)
In-Reply-To: <20211026165127.4151055-1-naohiro.aota@wdc.com>

On Wed, 27 Oct 2021 01:51:27 +0900, Naohiro Aota wrote:
> When dispatching a zone append write request to a SCSI zoned block device,
> if the target zone of the request is already locked, the device driver will
> return BLK_STS_ZONE_RESOURCE and the request will be pushed back to the
> hctx dipatch queue. The queue will be marked as RESTART in
> dd_finish_request() and restarted in __blk_mq_free_request(). However, this
> restart applies to the hctx of the completed request. If the requeued
> request is on a different hctx, dispatch will no be retried until another
> request is submitted or the next periodic queue run triggers, leading to up
> to 30 seconds latency for the requeued request.
> 
> [...]

Applied, thanks!

[1/1] block: schedule queue restart after BLK_STS_ZONE_RESOURCE
      commit: 9586e67b911c95ba158fcc247b230e9c2d718623

Best regards,
-- 
Jens Axboe



      reply	other threads:[~2021-10-26 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 16:51 [PATCH v2] block: schedule queue restart after BLK_STS_ZONE_RESOURCE Naohiro Aota
2021-10-26 22:00 ` 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=163528565626.259196.4840508461738349119.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Niklas.Cassel@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naohiro.aota@wdc.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;
as well as URLs for NNTP newsgroup(s).