[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220518230646.5xx6dpo4helwyqcv@garbanzo>
Date: Wed, 18 May 2022 16:06:46 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Theodore Ts'o <tytso@....edu>
Cc: Christoph Hellwig <hch@....de>,
Pankaj Raghav <p.raghav@...sung.com>, axboe@...nel.dk,
pankydev8@...il.com, gost.dev@...sung.com,
damien.lemoal@...nsource.wdc.com, jiangbo.365@...edance.com,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
dm-devel@...hat.com, dsterba@...e.com, linux-btrfs@...r.kernel.org
Subject: Re: [dm-devel] [PATCH v4 00/13] support non power of 2 zoned devices
On Tue, May 17, 2022 at 11:34:54AM -0400, Theodore Ts'o wrote:
> On Tue, May 17, 2022 at 10:10:48AM +0200, Christoph Hellwig wrote:
> > I'm a little surprised about all this activity.
> >
> > I though the conclusion at LSF/MM was that for Linux itself there
> > is very little benefit in supporting this scheme. It will massively
> > fragment the supported based of devices and applications, while only
> > having the benefit of supporting some Samsung legacy devices.
>
> FWIW,
>
> That wasn't my impression from that LSF/MM session, but once the
> videos become available, folks can decide for themselves.
Agreed, contrary to conventional storage devices, with the zone storage
ecosystem we simply have a requirement of zone drive replacements matching
zone size. That requirement exists for po2 or npo2. The work in this patch
set proves that supporting npo2 was in the end straight forward. As the one
putting together the BoF I can say that there were no sticking points raised
to move forward with this when the topic came up. So I am very surprised to
hear about any other perceived conclusion.
Luis
Powered by blists - more mailing lists