From: Wanpeng Li <wanpeng.li@linux.intel.com>
To: Chao Yu <chao2.yu@samsung.com>
Cc: 'Wanpeng Li' <wanpeng.li@linux.intel.com>,
'Jaegeuk Kim' <jaegeuk@kernel.org>,
'Changman Lee' <cm224.lee@samsung.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] f2fs: add fast symlink
Date: Thu, 12 Mar 2015 14:42:10 +0800 [thread overview]
Message-ID: <20150312064210.GA12364@kernel> (raw)
In-Reply-To: <009d01d05c7b$950dd970$bf298c50$@samsung.com>
Hi Chao,
On Thu, Mar 12, 2015 at 12:17:29PM +0800, Chao Yu wrote:
>
>We always remain space in inode page for inline xattr data,
>so it's better to define our max size of fast symlink as below:
>
>#define MAX_FAST_SYMLINK_SIZE (MAX_INLINE_DATA + 1)
>
Thanks for your review, I just handle all your comments and it works
well.
Btw, one question, if inline xattr data area is reserved in inode
even if it isn't mounted w/ inline_xattr option? If yes, why it
is reserved?
Regards,
Wanpeng Li
next prev parent reply other threads:[~2015-03-12 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 11:52 [PATCH RFC] f2fs: add fast symlink Wanpeng Li
2015-03-12 4:17 ` Chao Yu
2015-03-12 6:42 ` Wanpeng Li [this message]
2015-03-12 9:02 ` Chao Yu
2015-03-12 8:49 ` Wanpeng Li
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=20150312064210.GA12364@kernel \
--to=wanpeng.li@linux.intel.com \
--cc=chao2.yu@samsung.com \
--cc=cm224.lee@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).