[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFj5m9+o4yNA5rNDA+EXWZthMtB+dOLOW0O788i77=Qn1eJ0qQ@mail.gmail.com>
Date: Thu, 2 Mar 2023 17:14:13 +0800
From: Ming Lei <ming.lei@...hat.com>
To: Andreas Hindborg <nmi@...aspace.dk>
Cc: linux-block@...r.kernel.org, Hans Holmberg <Hans.Holmberg@....com>,
Matias Bjorling <Matias.Bjorling@....com>,
Niklas Cassel <Niklas.Cassel@....com>,
kernel test robot <lkp@...el.com>,
Jens Axboe <axboe@...nel.dk>,
open list <linux-kernel@...r.kernel.org>,
Damien Le Moal <damien.lemoal@...nsource.wdc.com>
Subject: Re: [PATCH v2] block: ublk: enable zoned storage support
On Thu, Mar 2, 2023 at 5:02 PM Ming Lei <ming.lei@...hat.com> wrote:
>
> 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.
oops, we have blk_zone_report data for reporting zones to userspace already,
see blkdev_report_zones_ioctl(), then this way can be re-used for getting zone
report from ublk server too, right?
Thanks,
Ming
Powered by blists - more mailing lists