From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <chao@kernel.org>
Subject: Re: [PATCH 1/2] f2fs: enable inline_xattr by default
Date: Wed, 15 Feb 2017 10:26:36 +0800 [thread overview]
Message-ID: <07aa0a06-b637-6588-c0d2-402134921ec0@huawei.com> (raw)
In-Reply-To: <20170214003502.GB14533@jaegeuk.local>
Hi Jaegeuk,
On 2017/2/14 8:35, Jaegeuk Kim wrote:
> Hi Chao,
>
> On 02/08, Chao Yu wrote:
>> In android, since SElinux is enable, security policy will be appliedd for
>> each file, it stores in inode as an xattr entry, so it will take one 4k
>> size node block additionally for each file.
>>
>> Let's enable inline_xattr by default in order to save storage space.
>
> Then, we need to add "noinline_xattr".
OK, let me introduce the new option in another patch.
Thanks,
>
> Thanks,
>
>>
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> fs/f2fs/super.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>> index 68a555b014cf..e2f919d3096a 100644
>> --- a/fs/f2fs/super.c
>> +++ b/fs/f2fs/super.c
>> @@ -1026,6 +1026,7 @@ static void default_options(struct f2fs_sb_info *sbi)
>> sbi->active_logs = NR_CURSEG_TYPE;
>>
>> set_opt(sbi, BG_GC);
>> + set_opt(sbi, INLINE_XATTR);
>> set_opt(sbi, INLINE_DATA);
>> set_opt(sbi, INLINE_DENTRY);
>> set_opt(sbi, EXTENT_CACHE);
>> --
>> 2.8.2.295.g3f1c1d0
>
> .
>
prev parent reply other threads:[~2017-02-15 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 9:39 Chao Yu
2017-02-08 9:39 ` [PATCH 2/2] f2fs: change recovery policy of xattr node block Chao Yu
2017-02-08 10:05 ` Chao Yu
2017-02-14 0:35 ` [PATCH 1/2] f2fs: enable inline_xattr by default Jaegeuk Kim
2017-02-15 2:26 ` Chao Yu [this message]
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=07aa0a06-b637-6588-c0d2-402134921ec0@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®