public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: Pankaj Raghav <p.raghav@samsung.com>,
	axboe@kernel.dk, pankydev8@gmail.com, gost.dev@samsung.com,
	damien.lemoal@opensource.wdc.com, jiangbo.365@bytedance.com,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	dm-devel@redhat.com, dsterba@suse.com,
	linux-btrfs@vger.kernel.org
Subject: Re: [dm-devel] [PATCH v4 00/13] support non power of 2 zoned devices
Date: Tue, 17 May 2022 11:34:54 -0400	[thread overview]
Message-ID: <YoPAnj9ufkt5nh1G@mit.edu> (raw)
In-Reply-To: <20220517081048.GA13947@lst.de>

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.

       	      		       	   	  - Ted

  parent reply	other threads:[~2022-05-17 15:36 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220516165418eucas1p2be592d9cd4b35f6b71d39ccbe87f3fef@eucas1p2.samsung.com>
2022-05-16 16:54 ` [PATCH v4 00/13] support non power of 2 zoned devices Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 01/13] block: make blkdev_nr_zones and blk_queue_zone_no generic for npo2 zsze Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 02/13] block: allow blk-zoned devices to have non-power-of-2 zone size Pankaj Raghav
2022-05-16 19:05     ` Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 03/13] nvme: zns: Allow ZNS drives that have non-power_of_2 " Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 04/13] nvmet: Allow ZNS target to support non-power_of_2 zone sizes Pankaj Raghav
2022-05-17 14:19     ` Johannes Thumshirn
2022-05-16 16:54   ` [PATCH v4 05/13] btrfs: zoned: Cache superblock location in btrfs_zoned_device_info Pankaj Raghav
2022-05-16 21:58     ` David Sterba
2022-05-17  7:55       ` Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 06/13] btrfs: zoned: Make sb_zone_number function non power of 2 compatible Pankaj Raghav
2022-05-17  6:53     ` Johannes Thumshirn
2022-05-17 11:51       ` David Sterba
2022-05-16 16:54   ` [PATCH v4 07/13] btrfs: zoned: use generic btrfs zone helpers to support npo2 zoned devices Pankaj Raghav
2022-05-17 12:30     ` David Sterba
2022-05-18  9:40       ` Pankaj Raghav
2022-05-18 11:21         ` David Sterba
2022-05-19  4:13     ` Naohiro Aota
2022-05-16 16:54   ` [PATCH v4 08/13] btrfs:zoned: make sb for npo2 zone devices align with sb log offsets Pankaj Raghav
2022-05-17  6:50     ` Johannes Thumshirn
2022-05-17  8:00       ` Pankaj Raghav
2022-05-17 12:42     ` David Sterba
2022-05-18  9:15       ` Pankaj Raghav
2022-05-19  7:57         ` Johannes Thumshirn
2022-05-20  9:06           ` Pankaj Raghav
2022-05-20  9:15             ` Johannes Thumshirn
2022-05-19  7:59     ` Naohiro Aota
2022-05-20  9:09       ` Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 09/13] btrfs: zoned: relax the alignment constraint for zoned devices Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 10/13] zonefs: allow non power of 2 " Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 11/13] null_blk: " Pankaj Raghav
2022-05-17  4:12     ` kernel test robot
2022-05-16 16:54   ` [PATCH v4 12/13] null_blk: use zone_size_sects_shift for " Pankaj Raghav
2022-05-16 16:54   ` [PATCH v4 13/13] dm-zoned: ensure only power of 2 zone sizes are allowed Pankaj Raghav
2022-05-17  8:10   ` [PATCH v4 00/13] support non power of 2 zoned devices Christoph Hellwig
2022-05-17  9:18     ` Javier González
2022-05-18  8:00       ` Christoph Hellwig
2022-05-19 15:25         ` Javier González
2022-05-17 15:34     ` Theodore Ts'o [this message]
2022-05-18 23:06       ` [dm-devel] " Luis Chamberlain
2022-05-19  3:08       ` Damien Le Moal
2022-05-19  3:12         ` Luis Chamberlain
2022-05-19  3:19           ` Damien Le Moal
2022-05-19  7:34             ` Johannes Thumshirn
2022-05-20  3:47               ` Damien Le Moal
2022-05-20  6:07                 ` Hannes Reinecke
2022-05-20  6:27                   ` Javier González
2022-05-20  6:41                     ` Damien Le Moal
2022-05-20  6:59                       ` Javier González
2022-05-20  9:30                       ` Pankaj Raghav
2022-05-20 17:18                         ` David Sterba
2022-05-23  8:25                           ` Pankaj Raghav
2022-05-20  9:30                     ` Johannes Thumshirn
2022-05-20 10:16                       ` Javier González
     [not found] <CGME20220516133922eucas1p1c891cd1d82539b4e792acb5d1aa74444@eucas1p1.samsung.com>
2022-05-16 13:39 ` Pankaj Raghav
2022-05-16 14:15   ` [dm-devel] " Damien Le Moal

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=YoPAnj9ufkt5nh1G@mit.edu \
    --to=tytso@mit.edu \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dm-devel@redhat.com \
    --cc=dsterba@suse.com \
    --cc=gost.dev@samsung.com \
    --cc=hch@lst.de \
    --cc=jiangbo.365@bytedance.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=p.raghav@samsung.com \
    --cc=pankydev8@gmail.com \
    /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