public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	Andreas Hindborg <a.hindborg@samsung.com>
Subject: Re: [PATCH] ublk: zoned: support REQ_OP_ZONE_RESET_ALL
Date: Thu, 10 Aug 2023 20:15:47 +0800	[thread overview]
Message-ID: <ZNTU8/hdhAo6Y/wx@fedora> (raw)
In-Reply-To: <ZNTPSQTDOgr7Ojn+@x1-carbon>

On Thu, Aug 10, 2023 at 11:51:38AM +0000, Niklas Cassel wrote:
> Hello Ming,
> 
> On Thu, Aug 10, 2023 at 05:20:57PM +0800, Ming Lei wrote:
> > There isn't any reason to not support REQ_OP_ZONE_RESET_ALL given everything
> > is actually handled in userspace, not mention it is pretty easy to support
> > RESET_ALL.
> > 
> > So enable REQ_OP_ZONE_RESET_ALL and let userspace handle it.
> > 
> > Verified by 'tools/zbc_reset_zone -all /dev/ublkb0' in libzbc[1] with
> > libublk-rs based ublk-zoned target prototype[2], follows command line
> > for creating ublk-zoned:
> > 
> > 	cargo run --example zoned -- add -1 1024	# add $dev_id $DEV_SIZE
> > 
> > [1] https://github.com/westerndigitalcorporation/libzbc
> > [2] https://github.com/ming1/libublk-rs/tree/zoned.v2
> > 
> > Cc: Damien Le Moal <dlemoal@kernel.org>
> > Cc: Andreas Hindborg <a.hindborg@samsung.com>
> > Signed-off-by: Ming Lei <ming.lei@redhat.com>
> > ---
> >  drivers/block/ublk_drv.c      | 5 ++++-
> >  include/uapi/linux/ublk_cmd.h | 1 +
> >  2 files changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/block/ublk_drv.c b/drivers/block/ublk_drv.c
> > index 109a5b17537d..939e4584485b 100644
> > --- a/drivers/block/ublk_drv.c
> > +++ b/drivers/block/ublk_drv.c
> > @@ -251,6 +251,7 @@ static int ublk_dev_param_zoned_apply(struct ublk_device *ub)
> >  	const struct ublk_param_zoned *p = &ub->params.zoned;
> >  
> >  	disk_set_zoned(ub->ub_disk, BLK_ZONED_HM);
> > +	blk_queue_flag_set(QUEUE_FLAG_ZONE_RESETALL, ub->ub_disk->queue);
> >  	blk_queue_required_elevator_features(ub->ub_disk->queue,
> >  					     ELEVATOR_F_ZBD_SEQ_WRITE);
> >  	disk_set_max_active_zones(ub->ub_disk, p->max_active_zones);
> > @@ -393,6 +394,9 @@ static blk_status_t ublk_setup_iod_zoned(struct ublk_queue *ubq,
> >  	case REQ_OP_ZONE_APPEND:
> >  		ublk_op = UBLK_IO_OP_ZONE_APPEND;
> >  		break;
> > +	case REQ_OP_ZONE_RESET_ALL:
> > +		ublk_op = UBLK_IO_OP_ZONE_RESET_ALL;
> > +		break;
> >  	case REQ_OP_DRV_IN:
> >  		ublk_op = pdu->operation;
> >  		switch (ublk_op) {
> > @@ -404,7 +408,6 @@ static blk_status_t ublk_setup_iod_zoned(struct ublk_queue *ubq,
> >  		default:
> >  			return BLK_STS_IOERR;
> >  		}
> > -	case REQ_OP_ZONE_RESET_ALL:
> >  	case REQ_OP_DRV_OUT:
> >  		/* We do not support reset_all and drv_out */
> 
> I think that you should also drop reset_all from this comment.

Good catch, will do it in v2.

Thanks,
Ming


      reply	other threads:[~2023-08-10 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  9:20 [PATCH] ublk: zoned: support REQ_OP_ZONE_RESET_ALL Ming Lei
2023-08-10 11:51 ` Niklas Cassel
2023-08-10 12:15   ` Ming Lei [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=ZNTU8/hdhAo6Y/wx@fedora \
    --to=ming.lei@redhat.com \
    --cc=Niklas.Cassel@wdc.com \
    --cc=a.hindborg@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox