From: Huajun Li <huajun.li.lee@gmail.com>
To: jaegeuk.kim@samsung.com, linux-f2fs-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Huajun Li <huajun.li@intel.com>
Subject: [f2fs-dev][PATCH V2 0/6] f2fs: Enable f2fs support inline data
Date: Sun, 10 Nov 2013 23:13:15 +0800 [thread overview]
Message-ID: <1384096401-25169-1-git-send-email-huajun.li.lee@gmail.com> (raw)
From: Huajun Li <huajun.li@intel.com>
f2fs inode is so large, so small files can be stored directly in the inode,
rather than just storing a single block address and storing the data elsewhere.
This patch set makes files less than ~3.4K store directly in inode block.
a) space saving
Test with kernel src(without repo data), it can save about 10% space
with this patch set;
b) performance
Test this patch set with iozone, there is no obvious performance difference
with the results of disabling this feature.
V2: - Update f2fs_reserve_block() according to comments on V1
- Add function f2fs_may_inline() to check whether the file meet
inline requirements
- Try to write inline data to normal data block before clearing it
from inode block
- Change lock scope while converting inline data
- Add inline_data description to f2fs documentation
Huajun Li (6):
f2fs: Add flags and helpers to support inline data
f2fs: Add a new mount option: inline_data
f2fs: Add a new function: f2fs_reserve_block()
f2fs: Key functions to handle inline data
f2fs: Handle inline data operations
f2fs: update f2fs Documentation
Documentation/filesystems/f2fs.txt | 2 +
fs/f2fs/Makefile | 2 +-
fs/f2fs/data.c | 97 +++++++++++++-------
fs/f2fs/f2fs.h | 23 +++++
fs/f2fs/file.c | 81 +++++++++--------
fs/f2fs/inline.c | 172 ++++++++++++++++++++++++++++++++++++
fs/f2fs/super.c | 8 +-
include/linux/f2fs_fs.h | 8 ++
8 files changed, 325 insertions(+), 68 deletions(-)
create mode 100644 fs/f2fs/inline.c
--
1.7.9.5
next reply other threads:[~2013-11-10 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 15:13 Huajun Li [this message]
2013-11-10 15:13 ` [PATCH V2 1/6] f2fs: Add flags and helpers to support inline data Huajun Li
2013-11-10 15:13 ` [PATCH V2 2/6] f2fs: Add a new mount option: inline_data Huajun Li
2013-11-10 15:13 ` [PATCH V2 3/6] f2fs: Add a new function: f2fs_reserve_block() Huajun Li
2013-11-25 11:05 ` [f2fs-dev][PATCH " Jaegeuk Kim
2013-11-10 15:13 ` [f2fs-dev][PATCH V2 4/6] f2fs: Key functions to handle inline data Huajun Li
2013-11-15 7:49 ` Jaegeuk Kim
2013-11-20 12:51 ` [PATCH " Huajun Li
2013-11-25 11:01 ` [f2fs-dev][PATCH " Jaegeuk Kim
2013-11-10 15:13 ` [PATCH V2 5/6] f2fs: Handle inline data operations Huajun Li
2013-11-10 15:13 ` [PATCH V2 6/6] f2fs: update f2fs Documentation Huajun Li
2013-11-26 7:45 ` [PATCH V2 0/6] f2fs: Enable f2fs support inline data Jaegeuk Kim
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=1384096401-25169-1-git-send-email-huajun.li.lee@gmail.com \
--to=huajun.li.lee@gmail.com \
--cc=huajun.li@intel.com \
--cc=jaegeuk.kim@samsung.com \
--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).