From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Luis Chamberlain <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Christoph Hellwig <firstname.lastname@example.org>,
Johannes Thumshirn <email@example.com>,
Dave Chinner <firstname.lastname@example.org>,
"Darrick J . Wong" <email@example.com>,
Hannes Reinecke <firstname.lastname@example.org>,
Matias Bjorling <Matias.Bjorling@wdc.com>
Subject: Re: [PATCH V2] fs: New zonefs file system
Date: Mon, 26 Aug 2019 04:39:33 +0000 [thread overview]
Message-ID: <BYAPR04MB5816B9DAA7DACD2DF62A0B3FE7A10@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
On 2019/08/23 7:44, Luis Chamberlain wrote:
> On Tue, Aug 20, 2019 at 05:12:49PM +0900, Damien Le Moal wrote:
>> The aggregated conventional zone file can be used as a regular file.
>> Operations such as the following work.
>> mkfs.ext4 /mnt/cnv/0
>> mount -o loop /mnt/cnv/0 /data
> Should BLK_DEV_LOOP_MIN_COUNT be increased if this is enabled to
> a mich higher sensible default? Right now the default is 8. Also,
> can we infer this later dynamically so so this can grow at proper
> scale without having to have user interaction?
I am not sure if this is really necessary, though I am not against it. I added
this in the commit message as as an example, simply because it is a very easy
way to test that the aggregated conventional zone file is working correctly. The
tendency these days it for drives to have very little, if any at all,
conventional zones. Even if they do, using dm-linear to chunk conventional and
sequential spaces into different block devices is probably a much better way to
separate the 2 zone types into different usage patterns.
> For now, I mean something like:
> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index 1bb8ec575352..22ba4803b075 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -217,7 +217,8 @@ config BLK_DEV_LOOP
> config BLK_DEV_LOOP_MIN_COUNT
> int "Number of loop devices to pre-create at init time"
> depends on BLK_DEV_LOOP
> - default 8
> + default 8 if !ZONEFS FILESYSTEM
> + default 32 if ZONEFS FILESYSTEM
> Static number of loop devices to be unconditionally pre-created
> at init time.
Since this is a simple fix, I think we could reserve it for later if the need
for this change increases due to zonefs ? The default value can also be
automatically inferred by counting the number of zoned disk in the system and
assuming one extra loop device for each zoned drive.
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2019-08-26 4:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 8:12 [PATCH V2] fs: New zonefs file system Damien Le Moal
2019-08-20 15:26 ` Darrick J. Wong
2019-08-21 1:05 ` Damien Le Moal
2019-08-21 1:43 ` Darrick J. Wong
2019-08-21 2:24 ` Damien Le Moal
2019-08-20 17:42 ` kbuild test robot
2019-08-22 22:43 ` Luis Chamberlain
2019-08-26 4:39 ` Damien Le Moal [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).