All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
	Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>,
	ming.lei@redhat.com
Subject: Re: [PATCH 2/2] block: Split and submit bios in LBA order
Date: Tue, 21 Mar 2023 10:17:37 +0800	[thread overview]
Message-ID: <ZBkTwV7UC5QDtRyj@ovpn-8-18.pek2.redhat.com> (raw)
In-Reply-To: <a9347617-70b3-3cc1-ea5e-c6bd78c29acd@opensource.wdc.com>

On Tue, Mar 21, 2023 at 10:46:30AM +0900, Damien Le Moal wrote:
> On 3/21/23 09:44, Ming Lei wrote:
> > On Mon, Mar 20, 2023 at 04:32:57PM -0700, Bart Van Assche wrote:
> >> On 3/20/23 16:28, Ming Lei wrote:
> >>> On Fri, Mar 17, 2023 at 04:45:46PM -0700, Bart Van Assche wrote:
> >>>> Thanks for having taken a look. This patch series is intended for
> >>>> REQ_OP_WRITE requests and not for REQ_OP_ZONE_APPEND requests.
> >>>
> >>> But you are talking about host-managed zoned device, and the write
> >>> should have to be zone append, right?
> >>
> >> Hi Ming,
> >>
> >> The use case I'm looking at is Android devices with UFS storage. UFS is
> >> based on SCSI and hence only REQ_OP_WRITE is supported natively. There is a
> >> REQ_OP_ZONE_APPEND emulation in drivers/scsi/sd_zbc.c but it restricts the
> >> queue depth to one.
> > 
> > But is this UFS one host-managed zoned device? If yes, this "REQ_OP_WRITE"
> > still should have been handled as REQ_OP_ZONE_APPEND? Otherwise, I don't
> > think it is host-managed, and your patch isn't needed too.
> 
> Ming,
> 
> Both regular writes and zone append writes are supported by host managed
> devices. For ZNS, zone append write is natively supported as a different
> command. For SCSI & ATA (and UFS) devices, zone append write is emulated in the
> sd driver using the regular write command because the SCSI and ATA standards do
> not define a zone append write command.

Thanks for the clarification.

> 
> For BIO splitting, splitting a regular write is fine as the resulting fragments
> are sequential writes, so all fine. But zone append splitting is not allowed as

The current bio split code may not make sequential write requests, and
looks Bart is trying to address it. Then looks scsi zdc emulation still
requires sequential writes aiming to same zone.

But I guess it is hard to maintain bio order, especially md/dm is
involved.

Thanks, 
Ming


  reply	other threads:[~2023-03-21  2:18 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 19:59 [PATCH 0/2] Submit split bios in LBA order Bart Van Assche
2023-03-17 19:59 ` [PATCH 1/2] block: Split blk_recalc_rq_segments() Bart Van Assche
2023-03-18  6:38   ` Christoph Hellwig
2023-03-17 19:59 ` [PATCH 2/2] block: Split and submit bios in LBA order Bart Van Assche
2023-03-17 22:28   ` Jan Kara
2023-03-18  6:33     ` Christoph Hellwig
2023-03-17 23:38   ` Ming Lei
2023-03-17 23:45     ` Bart Van Assche
2023-03-20 23:28       ` Ming Lei
2023-03-20 23:32         ` Bart Van Assche
2023-03-21  0:44           ` Ming Lei
2023-03-21  1:46             ` Damien Le Moal
2023-03-21  2:17               ` Ming Lei [this message]
2023-03-21  3:24                 ` Damien Le Moal
2023-03-21  8:00                   ` Ming Lei
2023-03-21  8:51                     ` Damien Le Moal
2023-03-21  9:09                       ` Christoph Hellwig
2023-03-21  9:50                         ` Damien Le Moal
2023-03-21  5:55           ` Christoph Hellwig
2023-03-21 14:36             ` Bart Van Assche
2023-03-23  8:26               ` Christoph Hellwig
2023-03-23 10:28                 ` Damien Le Moal
2023-03-23 16:27                   ` Bart Van Assche
2023-03-23 22:53                     ` Damien Le Moal
2023-03-24 16:55                       ` Bart Van Assche
2023-03-25  2:00                         ` Damien Le Moal
2023-03-25 16:31                           ` Bart Van Assche
2023-03-26  1:45                             ` Damien Le Moal
2023-03-26 23:45                               ` Christoph Hellwig
2023-03-27 21:06                                 ` Bart Van Assche
2023-03-27 23:43                                   ` Christoph Hellwig
2023-04-06 20:30                                     ` Bart Van Assche
2023-03-27 21:20                               ` Bart Van Assche
2023-03-18  6:42   ` Christoph Hellwig
2023-03-18  6:29 ` [PATCH 0/2] Submit split " Christoph Hellwig
2023-03-20 17:22   ` Bart Van Assche
2023-03-20 21:06     ` Khazhy Kumykov
2023-03-23  8:27     ` Christoph Hellwig
2023-03-24 17:05       ` Bart Van Assche
2023-03-25  2:15         ` Damien Le Moal
2023-03-26 23:42           ` Christoph Hellwig
2023-03-26 23:44         ` Christoph Hellwig
2023-04-06 20:32           ` 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=ZBkTwV7UC5QDtRyj@ovpn-8-18.pek2.redhat.com \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=jaegeuk@kernel.org \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-block@vger.kernel.org \
    /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.