All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Andreas Hindborg <nmi@metaspace.dk>
Cc: linux-block@vger.kernel.org,
	Hans Holmberg <Hans.Holmberg@wdc.com>,
	Matias Bjorling <Matias.Bjorling@wdc.com>,
	Niklas Cassel <Niklas.Cassel@wdc.com>,
	kernel test robot <lkp@intel.com>, Jens Axboe <axboe@kernel.dk>,
	open list <linux-kernel@vger.kernel.org>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH v2] block: ublk: enable zoned storage support
Date: Thu, 2 Mar 2023 17:01:53 +0800	[thread overview]
Message-ID: <ZABmAR6Du1tUVEa7@T590> (raw)
In-Reply-To: <ZABfFW+28Jlxq+Ew@T590>

On Thu, Mar 02, 2023 at 04:32:21PM +0800, Ming Lei wrote:
> On Thu, Mar 02, 2023 at 08:31:07AM +0100, Andreas Hindborg wrote:
> > 

...

> > 
> > I agree about fetching more zones. However, it is no good to fetch up to
> > a max, since the requested zone report may less than max. I was
> 
> Short read should always be supported, so the interface may need to 
> return how many zones in single command, please refer to nvme_ns_report_zones().

blk_zone is part of uapi, maybe the short read can be figured out by
one all-zeroed 'blk_zone'?  then no extra uapi data is needed for
reporting zones.


thanks,
Ming


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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 20:05 [PATCH v2] block: ublk: enable zoned storage support Andreas Hindborg
2023-02-27 10:20 ` Niklas Cassel
2023-02-27 11:59   ` Andreas Hindborg
2023-02-27 14:29     ` Niklas Cassel
2023-02-27 14:41       ` Andreas Hindborg
2023-02-27 15:20 ` Minwoo Im
2023-02-27 15:36   ` Andreas Hindborg
2023-02-28  9:52 ` Hans Holmberg
2023-03-01  7:28   ` Andreas Hindborg
2023-03-02  2:50 ` Ming Lei
2023-03-02  7:31   ` Andreas Hindborg
2023-03-02  8:19     ` Damien Le Moal
2023-03-02  8:32     ` Ming Lei
2023-03-02  9:01       ` Ming Lei [this message]
2023-03-02  9:14         ` Ming Lei
2023-03-02 10:07           ` Andreas Hindborg
2023-03-02 13:16             ` Ming Lei
2023-03-02 13:28               ` Andreas Hindborg
2023-03-03  2:59                 ` Ming Lei
2023-03-03  8:27                   ` Andreas Hindborg
2023-03-03 11:47                     ` Ming Lei

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=ZABmAR6Du1tUVEa7@T590 \
    --to=ming.lei@redhat.com \
    --cc=Hans.Holmberg@wdc.com \
    --cc=Matias.Bjorling@wdc.com \
    --cc=Niklas.Cassel@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nmi@metaspace.dk \
    /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.