linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Li Guifu <blucerlee@gmail.com>
To: Gao Xiang <hsiangkao@aol.com>,
	Li Guifu <bluce.liguifu@huawei.com>, Chao Yu <yuchao0@huawei.com>,
	linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH 2/2] erofs-utils: introduce shared xattr support
Date: Sun, 6 Oct 2019 00:43:21 +0800	[thread overview]
Message-ID: <ace894c2-f2f6-9c1a-80d3-045bdc9ee0eb@gmail.com> (raw)
In-Reply-To: <20191005142050.8827-2-hsiangkao@aol.com>

> From: Li Guifu <blucerlee@gmail.com>
> 
> Large xattrs or xattrs shared by a lot of files
> can be stored in shared xattrs rather than
> inlined right after inode.
> 
> Signed-off-by: Li Guifu <blucerlee@gmail.com>
> Signed-off-by: Gao Xiang <hsiangkao@aol.com>

Dear Gao Xiang,
   Should It need to add a configure parameter to 
cfg.c_inline_xattr_tolerance which is a custome threshold
of shared xattr ?

  reply	other threads:[~2019-10-05 16:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 11:50 [PATCH] erofs-utils: introduce xattr support htyuxe+dhbrei4sq0df8
2019-08-05 14:54 ` Li Guifu
2019-08-05 17:30   ` Gao Xiang
2019-08-11 17:10     ` [PATCH v2] erofs-utils: introduce preliminary " Gao Xiang
2019-10-05 14:20       ` [PATCH v3 1/2] erofs-utils: introduce inline " Gao Xiang via Linux-erofs
2019-10-05 14:20         ` [PATCH 2/2] erofs-utils: introduce shared " Gao Xiang via Linux-erofs
2019-10-05 16:43           ` Li Guifu [this message]
2019-10-06  5:01             ` Gao Xiang via Linux-erofs
2019-10-14 11:42               ` [PATCH v4 1/2] erofs-utils: introduce inline " Gao Xiang via Linux-erofs
2019-10-14 11:42                 ` [PATCH v4 2/2] erofs-utils: introduce shared " Gao Xiang via Linux-erofs
2019-10-14 23:53                   ` [PATCH v5 " Gao Xiang via Linux-erofs
2019-10-05 16:44         ` [PATCH v3 1/2] erofs-utils: introduce inline " Li Guifu

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=ace894c2-f2f6-9c1a-80d3-045bdc9ee0eb@gmail.com \
    --to=blucerlee@gmail.com \
    --cc=bluce.liguifu@huawei.com \
    --cc=hsiangkao@aol.com \
    --cc=linux-erofs@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).