public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	Hannes Reinecke <hare@suse.de>, Ting Yao <d201577678@hust.edu.cn>
Subject: Re: [PATCH RFC] fs: New zonefs file system
Date: Mon, 22 Jul 2019 10:12:00 +1000	[thread overview]
Message-ID: <20190722001200.GQ7689@dread.disaster.area> (raw)
In-Reply-To: <BYAPR04MB5816A2630B1EBC0696CBEC71E7CA0@BYAPR04MB5816.namprd04.prod.outlook.com>

On Sat, Jul 20, 2019 at 01:07:25AM +0000, Damien Le Moal wrote:
> On 2019/07/19 23:25, Jeff Moyer wrote:
> > I'll throw out another suggestion that may or may not work (I haven't
> > given it much thought).  Would it be possible to create a device mapper
> > target that would export each zone as a separate block device?  I
> > understand that wouldn't help with the write pointer management, but it
> > would allow you to create a single "file" for each zone.
> 
> Well, I do not think you need a new device mapper for this. dm-linear supports
> zoned block devices and will happily allow mapping a single zone and expose a
> block device file for it. My problem with this approach is that SMR drives are
> huge, and getting bigger. A 15 TB drive has 55380 zones of 256 MB. Upcoming 20
> TB drives have more than 75000 zones. Using dm-linear or any per-zone device
> mapper target would create a huge resources pressure as the amount of memory
> alone that would be used per zone would be much higher than with a file system
> and the setup would also take far longer to complete compared to zonefs mount.

Right, it's kinda insane to expect userspace to manage tens of
thousands of "block devices" like this. You go run blkid on one of
these devices, and what happens? Then there's stuff like udev
overhead, grub os-probing that walks all block devices it can find,
etc. Then consider putting hundreds of SMR drives into a machine
that has multiple paths to each drive....

As such, I just don't think this block device approach is feasible,
especially as Managing tens of thousands of individual small data
regions in a storage device is exactly what filesystems are for.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2019-07-22  0:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  3:00 [PATCH RFC] fs: New zonefs file system Damien Le Moal
2019-07-12  8:00 ` Johannes Thumshirn
2019-07-12  8:31   ` Damien Le Moal
2019-07-12  8:47     ` Johannes Thumshirn
2019-07-12 17:10 ` Viacheslav Dubeyko
2019-07-12 22:56   ` Damien Le Moal
2019-07-15 16:54     ` Viacheslav Dubeyko
2019-07-15 23:53       ` Damien Le Moal
2019-07-16 16:51         ` Viacheslav Dubeyko
2019-07-18  0:57           ` Damien Le Moal
2019-07-15  1:19 ` Dave Chinner
2019-07-15  6:57   ` Johannes Thumshirn
2019-07-16 11:21   ` Damien Le Moal
2019-07-18 14:11 ` Jeff Moyer
2019-07-18 23:02   ` Damien Le Moal
2019-07-19 14:25     ` Jeff Moyer
2019-07-19 14:25       ` Jeff Moyer
2019-07-20  1:07       ` Damien Le Moal
2019-07-22  0:12         ` Dave Chinner [this message]
2019-07-20  7:15       ` Damien Le Moal
2019-07-22  0:04         ` Dave Chinner
2019-07-22  0:09           ` 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=20190722001200.GQ7689@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=d201577678@hust.edu.cn \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jmoyer@redhat.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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