All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
	Ming Lei <ming.lei@redhat.com>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH v2 3/3] block: Preserve LBA order when requeuing
Date: Tue, 21 Mar 2023 07:46:51 -0700	[thread overview]
Message-ID: <6325fba6-3dac-9391-28ef-177fcae9ad0a@acm.org> (raw)
In-Reply-To: <20230321055802.GA18078@lst.de>

On 3/20/23 22:58, Christoph Hellwig wrote:
> On Mon, Mar 20, 2023 at 04:49:05PM -0700, Bart Van Assche wrote:
>> When requeuing a request to a zoned block device, preserve the LBA order
>> per zone.
> 
> What causes this requeue?

Hi Christoph,

Two examples of why the SCSI core can decide to requeue a command are a 
retryable unit attention or ufshcd_queuecommand() returning 
SCSI_MLQUEUE_HOST_BUSY. For example, ufshcd_queuecommand() returns 
SCSI_MLQUEUE_HOST_BUSY while clock scaling is in progress (changing the 
frequency of the link between host controller and UFS device).

Thanks,

Bart.

  reply	other threads:[~2023-03-21 14:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 23:49 [PATCH v2 0/3] Submit zoned requests in LBA order per zone Bart Van Assche
2023-03-20 23:49 ` [PATCH v2 1/3] block: Split blk_recalc_rq_segments() Bart Van Assche
2023-03-20 23:49 ` [PATCH v2 2/3] block: Split and submit bios in LBA order Bart Van Assche
2023-03-21  6:03   ` Christoph Hellwig
2023-03-21  6:05     ` Christoph Hellwig
2023-03-21 18:44       ` Bart Van Assche
2023-03-23  8:22         ` Christoph Hellwig
2023-03-20 23:49 ` [PATCH v2 3/3] block: Preserve LBA order when requeuing Bart Van Assche
2023-03-21  5:58   ` Christoph Hellwig
2023-03-21 14:46     ` Bart Van Assche [this message]
2023-03-23  8:19       ` 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=6325fba6-3dac-9391-28ef-177fcae9ad0a@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=johannes.thumshirn@wdc.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.