From: Chao Yu <yuchao0@huawei.com>
To: Patrick Doyle <wpdster@gmail.com>, chao@kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Are there limitation to the number of named pipes/FIFO's supported by F2FS?
Date: Thu, 6 Sep 2018 10:03:58 +0800 [thread overview]
Message-ID: <2d8ae907-a7ac-446c-d31e-d3c66ee4d8f6@huawei.com> (raw)
In-Reply-To: <CAF_dkJAzcBui=6ov=gbob3-T8u2n3QUyn3znSbLUkFjeg7nB8g@mail.gmail.com>
On 2018/9/6 0:11, Patrick Doyle wrote:
> What is the "Large nat bitmap feature"? (Now you've got me curious).
That's the feature backed '-i' option, it can make image support more inode
space.
So if you use this feature in f2fs version lower than 4.17, there should be
problem.
>
> Would that have been turned on by default with the 1.11.0 version of
> mkfs.f2fs I used to gain access to the "-i" option?
Not sure, in android scenario, I haven't got any report that in 256GB size
cell phone, it runs out of inode space.
To Jaegeuk,
Maybe, we could give a hint (leaving a message) to user to use '-i' option
if partition size is large, e.g. >= 512MB?
Thanks,
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-09-06 2:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 16:28 Are there limitation to the number of named pipes/FIFO's supported by F2FS? Patrick Doyle
2018-09-05 1:55 ` Chao Yu
2018-09-05 4:12 ` Jaegeuk Kim
2018-09-05 13:35 ` Patrick Doyle
2018-09-05 15:57 ` Chao Yu
2018-09-05 16:11 ` Patrick Doyle
2018-09-05 17:30 ` Jaegeuk Kim
2018-09-06 1:51 ` Chao Yu
2018-09-06 13:14 ` Patrick Doyle
2018-09-06 13:29 ` Chao Yu
2018-09-06 2:03 ` Chao Yu [this message]
2018-09-06 12:44 ` Chao Yu
2018-09-06 13:31 ` Patrick Doyle
2018-09-05 17:16 ` Jaegeuk Kim
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=2d8ae907-a7ac-446c-d31e-d3c66ee4d8f6@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=wpdster@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;
as well as URLs for NNTP newsgroup(s).