From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [RFC PATCH] f2fs-tools: introduce tune.f2fs
Date: Mon, 7 May 2018 20:25:14 +0800 [thread overview]
Message-ID: <3be5fc55-96ac-b70e-5a1f-ef3d7ea84e23@huawei.com> (raw)
In-Reply-To: <20180504190607.GE27993@jaegeuk-macbookpro.roam.corp.google.com>
On 2018/5/5 3:06, Jaegeuk Kim wrote:
> On 05/02, Chao Yu wrote:
>> On 2018/4/28 10:49, Jaegeuk Kim wrote:
>>> On 04/27, Chao Yu wrote:
>>>> On 2018/4/27 0:13, Jaegeuk Kim wrote:
>>>>> On 04/26, Junling Zheng wrote:
>>>>>> Ping...
>>>>>>
>>>>>> On 2018/4/23 15:32, Junling Zheng wrote:
>>>>>>> Introduce tune.f2fs tool to change the f2fs parameters.
>>>>>>> Currently this tool only supports adding or removing encrypt
>>>>>>> feature bit in superblock.
>>>>>
>>>>> What is the purpose of this empty tune.f2fs? How can we say we have this
>>>>> tool to users? You have to design what kind of things to support first.
>>>>
>>>> I checked very initial tune2fs.c, it only supports very few parameters tuning
>>>> functionality, but, can not say that is a bad start to introduce the misc tool.
>>>>
>>>> + fprintf (stderr, "Usage: %s [-c max-mounts-count] [-e errors-behavior] "
>>>> + "[-i interval[d|m]]\n"
>>>> + "\t[-l] [-m reserved-blocks-percent] device\n", program_name);
>>>
>>> I don't think We have to follow that.
>>>
>>>>
>>>> Maybe tuning 1. extension list, 2. multi device name later? just guess.
>>>
>>> First of all, does it make sense to unset feature bits? I don't think so.
>>
>> Some features can be turned off in a initial image? like encrypted, extra_attr,
>> checksum...?
>
> Any reason to do thtat? And, we need to find all the files whether there is
Not very sure, just checked tune2fs, and found them in manual, guessing that
there came demand from user who want to disable some feature in a formatted
partition?
> any encrypted file.
>
>>
>>>
>>> Agreed to your suggestion where:
>>> 1. feature set
>>> - enable system quota
>>> 2. extension list
>>> 3. multi device name -- which may be really big trial
>>
>> So what's our plan now? fill those features into fsck when we need them?
>
> No. If you want to add tune.f2fs, I'd like to see some demand, or very useful
> features like this. I just want to avoid introducing an (almost) empty tool.
Yeah, I see.
Maybe we can support below options except feature/extension_list/device_name.
-Q quota-options set,clear user/group/prjquota sysfile inode.
-U UUID set,clear uuid
-L volume-label set,clear volume name
Thanks,
>
> Thanks,
>
>>
>> Thanks,
>>
>>>
>>>>
>>>> Using fsck.f2fs to tune parameter, IMO, maybe a little confuse for user to
>>>> understand the tool's functionality.
>>>>
>>>> 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-05-07 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 20:54 [PATCH] fsck.f2fs: add -O features to tune the bits Jaegeuk Kim
2018-04-20 1:46 ` Junling Zheng
2018-04-20 1:57 ` Chao Yu
2018-04-20 2:52 ` Jaegeuk Kim
2018-04-23 7:32 ` [RFC PATCH] f2fs-tools: introduce tune.f2fs Junling Zheng
2018-04-26 2:10 ` Junling Zheng
2018-04-26 16:13 ` Jaegeuk Kim
2018-04-27 2:32 ` Chao Yu
2018-04-28 2:49 ` Jaegeuk Kim
2018-05-02 2:20 ` Chao Yu
2018-05-04 19:06 ` Jaegeuk Kim
2018-05-07 12:25 ` Chao Yu [this message]
2018-04-23 3:55 ` [PATCH] fsck.f2fs: add -O features to tune the bits Chao Yu
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=3be5fc55-96ac-b70e-5a1f-ef3d7ea84e23@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).