From: Gioh Kim <gioh.kim@lge.com>
To: gioh.kim@lge.com, akpm@linux-foundation.org, jack@suse.cz,
tytso@mit.edu, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, paulmck@linux.vnet.ibm.com,
peterz@infradead.org, adilger.kernel@dilger.ca
Cc: minchan@kernel.org, js1304@gmail.com, gunho.lee@lge.com
Subject: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag
Date: Thu, 4 Sep 2014 16:29:38 +0900 [thread overview]
Message-ID: <1409815781-28011-1-git-send-email-gioh.kim@lge.com> (raw)
Hello,
This patch try to solve problem that a long-lasting page caches of
ext4 superblock and journaling of superblock disturb page migration.
I've been testing CMA feature on my ARM-based platform
and found that two page caches cannot be migrated.
They are page caches of superblock of ext4 filesystem and its journaling data.
Current ext4 reads superblock with sb_bread() that allocates page
from movable area. But the problem is that ext4 hold the page until
it is unmounted. If root filesystem is ext4 the page cannot be migrated
forever.
And also the journaling data for the superblock cannot be migreated.
I introduce new APIs that allocates page cache with specific flag passed by an
argument.
*_gfp APIs are for user want to set page allocation flag for page cache
allocation.
And *_unmovable APIs are for the user wants to allocate page cache from
non-movable area.
It is useful for ext4/ext3 and others that want to hold page cache for a long
time.
I have 3 patchs:
1. Patch 1/3: introduce a new API that create page cache with allocation flag
2. Patch 2/3: have ext4 use the new API to read superblock
3. Patch 3/3: have jbd/jbd2 use the new API to make journaling of superblock
This patchset is based on linux-next-20140814.
Thanks a lot.
Gioh Kim (3):
fs.c: support buffer cache allocations with gfp modifiers
ext4: use non-movable memory for the ext4 superblock
jbd/jbd2: use non-movable memory for the jbd superblock
fs/buffer.c | 45 ++++++++++++++++++++++++-----------------
fs/ext4/super.c | 6 +++---
fs/jbd/journal.c | 2 +-
fs/jbd2/journal.c | 2 +-
include/linux/buffer_head.h | 47 ++++++++++++++++++++++++++++++++++++++-----
5 files changed, 73 insertions(+), 29 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-09-04 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 7:29 Gioh Kim [this message]
2014-09-04 7:29 ` [PATCHv4 1/3] fs.c: support buffer cache allocations with gfp modifiers Gioh Kim
2014-09-05 2:37 ` Theodore Ts'o
2014-09-04 7:29 ` [PATCHv4 2/3] ext4: use non-movable memory for the ext4 superblock Gioh Kim
2014-09-05 2:37 ` Theodore Ts'o
2014-09-04 7:29 ` [PATCHv4 3/3] jbd/jbd2: use non-movable memory for the jbd superblock Gioh Kim
2014-09-05 2:37 ` Theodore Ts'o
2014-09-04 22:16 ` [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag Andrew Morton
2014-09-05 0:37 ` Gioh Kim
2014-09-05 1:14 ` Theodore Ts'o
2014-09-05 1:48 ` Joonsoo Kim
2014-09-05 3:17 ` Theodore Ts'o
2014-09-05 7:32 ` Joonsoo Kim
2014-09-05 14:14 ` Theodore Ts'o
2014-09-15 1:10 ` Joonsoo Kim
2014-09-15 6:37 ` Minchan 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=1409815781-28011-1-git-send-email-gioh.kim@lge.com \
--to=gioh.kim@lge.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=gunho.lee@lge.com \
--cc=jack@suse.cz \
--cc=js1304@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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®