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 0/5] f2fs: Enable f2fs support inline data
Date: Sat, 26 Oct 2013 00:01:54 +0800 [thread overview]
Message-ID: <1382716919-23345-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.
Huajun Li (5):
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 read and write
fs/f2fs/Makefile | 2 +-
fs/f2fs/data.c | 77 ++++++++++++++++++++-----
fs/f2fs/f2fs.h | 22 ++++++++
fs/f2fs/file.c | 42 +++++++++++++-
fs/f2fs/inline.c | 144 +++++++++++++++++++++++++++++++++++++++++++++++
fs/f2fs/super.c | 8 ++-
include/linux/f2fs_fs.h | 8 +++
7 files changed, 283 insertions(+), 20 deletions(-)
create mode 100644 fs/f2fs/inline.c
--
1.7.9.5
next reply other threads:[~2013-10-25 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 16:01 Huajun Li [this message]
2013-10-25 16:01 ` [f2fs-dev 1/5] f2fs: Add flags and helpers to support inline data Huajun Li
2013-10-25 16:01 ` [f2fs-dev 2/5] f2fs: Add a new mount option: inline_data Huajun Li
2013-10-25 16:01 ` [f2fs-dev 3/5] f2fs: Add a new function: f2fs_reserve_block() Huajun Li
[not found] ` <1382962607.992.104.camel@kjgkr>
2013-10-28 12:28 ` Jaegeuk Kim
2013-10-28 16:53 ` Huajun Li
2013-10-29 0:56 ` Jaegeuk Kim
2013-10-29 15:27 ` Huajun Li
2013-10-25 16:01 ` [f2fs-dev 4/5] f2fs: Key functions to handle inline data Huajun Li
2013-10-28 12:43 ` Jaegeuk Kim
2013-10-28 17:20 ` Huajun Li
2013-10-29 1:06 ` Jaegeuk Kim
2013-10-29 15:33 ` Huajun Li
2013-10-25 16:01 ` [f2fs-dev 5/5] f2fs: Handle inline data operations Huajun Li
2013-10-28 12:44 ` Jaegeuk Kim
2013-10-28 16:56 ` Huajun 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=1382716919-23345-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).