From: Luis Chamberlain <mcgrof@kernel.org>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
Dave Chinner <david@fromorbit.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Hannes Reinecke <hare@suse.de>,
Matias Bjorling <matias.bjorling@wdc.com>
Subject: Re: [PATCH V2] fs: New zonefs file system
Date: Thu, 22 Aug 2019 22:43:55 +0000 [thread overview]
Message-ID: <20190822224355.GX30113@42.do-not-panic.com> (raw)
In-Reply-To: <20190820081249.27353-1-damien.lemoal@wdc.com>
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?
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
help
Static number of loop devices to be unconditionally pre-created
at init time.
Luis
next prev parent reply other threads:[~2019-08-22 22:44 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 [this message]
2019-08-26 4:39 ` 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=20190822224355.GX30113@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=damien.lemoal@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=matias.bjorling@wdc.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;
as well as URLs for NNTP newsgroup(s).