linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Ming Lei <ming.lei@redhat.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH v5 3/7] scsi: core: Retry unaligned zoned writes
Date: Wed, 2 Aug 2023 18:12:23 +0900	[thread overview]
Message-ID: <ce950bef-1ae9-fcee-70f6-90adaef0aa25@kernel.org> (raw)
In-Reply-To: <20230731221458.437440-4-bvanassche@acm.org>

On 8/1/23 07:14, Bart Van Assche wrote:
> If zoned writes (REQ_OP_WRITE) for a sequential write required zone have
> a starting LBA that differs from the write pointer, e.g. because zoned
> writes have been reordered, then the storage device will respond with an
> UNALIGNED WRITE COMMAND error. Send commands that failed with an
> unaligned write error to the SCSI error handler if zone write locking is
> disabled. Let the SCSI error handler sort SCSI commands per LBA before
> resubmitting these.
> 
> If zone write locking is disabled, increase the number of retries for
> write commands sent to a sequential zone to the maximum number of
> outstanding commands because in the worst case the number of times
> reordered zoned writes have to be retried is (number of outstanding
> writes per sequential zone) - 1.
> 
> Cc: Martin K. Petersen <martin.petersen@oracle.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Damien Le Moal <dlemoal@kernel.org>
> Cc: Ming Lei <ming.lei@redhat.com>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>

Looks OK.

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2023-08-02  9:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 22:14 [PATCH v5 0/7] Improve the performance for zoned UFS devices Bart Van Assche
2023-07-31 22:14 ` [PATCH v5 1/7] block: Introduce the flag QUEUE_FLAG_NO_ZONE_WRITE_LOCK Bart Van Assche
2023-08-02  9:12   ` Damien Le Moal
2023-07-31 22:14 ` [PATCH v5 2/7] block/mq-deadline: Only use zone locking if necessary Bart Van Assche
2023-08-02  9:12   ` Damien Le Moal
2023-07-31 22:14 ` [PATCH v5 3/7] scsi: core: Retry unaligned zoned writes Bart Van Assche
2023-08-02  9:12   ` Damien Le Moal [this message]
2023-08-02  9:16   ` Hannes Reinecke
2023-08-02  9:31     ` Damien Le Moal
2023-08-02 11:52   ` Christoph Hellwig
2023-08-02 17:20     ` Bart Van Assche
2023-07-31 22:14 ` [PATCH v5 4/7] scsi: scsi_debug: Support disabling zone write locking Bart Van Assche
2023-08-07 18:13   ` Douglas Gilbert
2023-07-31 22:14 ` [PATCH v5 5/7] scsi: scsi_debug: Support injecting unaligned write errors Bart Van Assche
2023-08-07 18:13   ` Douglas Gilbert
2023-07-31 22:14 ` [PATCH v5 6/7] scsi: ufs: Split an if-condition Bart Van Assche
2023-07-31 22:14 ` [PATCH v5 7/7] scsi: ufs: Disable zone write locking Bart Van Assche

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=ce950bef-1ae9-fcee-70f6-90adaef0aa25@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=jejb@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --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 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).