mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
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: Mon, 13 Feb 2017 16:35:02 -0800	[thread overview]
Message-ID: <20170214003502.GB14533@jaegeuk.local> (raw)
In-Reply-To: <20170208093945.24681-1-yuchao0@huawei.com>

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".

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

  parent reply	other threads:[~2017-02-14  0:35 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 ` Jaegeuk Kim [this message]
2017-02-15  2:26   ` [PATCH 1/2] f2fs: enable inline_xattr by default 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=20170214003502.GB14533@jaegeuk.local \
    --to=jaegeuk@kernel.org \
    --cc=chao@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.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

all inboxes | Powered by JetHome®