public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "hch@infradead.org" <hch@infradead.org>,
	Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"hch@lst.de" <hch@lst.de>, "hare@suse.de" <hare@suse.de>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	Bart Van Assche <Bart.VanAssche@wdc.com>
Subject: Re: [PATCH] scsi: sd_zbc: Disable zoned block devices with scsi-mq
Date: Thu, 17 Aug 2017 15:01:51 +0000	[thread overview]
Message-ID: <1502982108.2615.1.camel@wdc.com> (raw)
In-Reply-To: <2b78a557-d573-9ba1-0068-56417042ffc8@wdc.com>

On Thu, 2017-08-17 at 21:19 +0900, Damien Le Moal wrote:
> On 8/17/17 16:59, Christoph Hellwig wrote:
> > On Thu, Aug 17, 2017 at 11:45:50AM +0900, Damien Le Moal wrote:
> > > blk-mq may not maintain write requests order at dispatch time. So host
> > > managed drives will not reliably work. Worse, potential reordering of
> > > write requests on requeue may cause the zone write locking code to
> > > deadlock command dispatch to the disk. So for now, until the write
> > > ordering issue is fixed, do not support zoned block devices with
> > > scsi-mq by showing a 0 LBA capacity disk.
> > 
> > NAK.  Please fix the issue instead of this.
> 
> I do have a fix ready to send. All the fixes are at blk-mq level and
> basically ensure that dispatch from the hctx->dispatch list are in order
> for write commands (regular writes, write same and write zeroes).
> It is well tested and at least fixes all the problems I have seen with
> dm-zoned and f2fs.

Hello Damien,

Another possible approach is to fix the ipr driver and to resubmit the
"scsi-mq: Always unprepare before requeuing a request" and "scsi: sd_zbc:
Write unlock zone from sd_uninit_cmnd()" patches.

Bart.

  parent reply	other threads:[~2017-08-17 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  2:45 [PATCH] scsi: sd_zbc: Disable zoned block devices with scsi-mq Damien Le Moal
2017-08-17  7:59 ` Christoph Hellwig
2017-08-17 12:19   ` Damien Le Moal
2017-08-17 12:24     ` Damien Le Moal
2017-08-17 15:01     ` Bart Van Assche [this message]
2017-08-18  0:21       ` Damien Le Moal
2017-08-21 15:33       ` hch
2017-08-21 20:31         ` Martin K. Petersen

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=1502982108.2615.1.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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