public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gioh Kim <gioh.kim@lge.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Theodore Ts'o" <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org
Subject: [PATCH 0/2] new API to allocate buffer-cache for superblock in non-movable area
Date: Tue, 22 Jul 2014 14:18:47 +0900	[thread overview]
Message-ID: <53CDF437.4090306@lge.com> (raw)

Hello,

This patch try to solve problem that a long-lasting page cache of
ext4 superblock disturbs page migration.

I've been testing CMA feature on my ARM-based platform
and found some pages for page caches cannot be migrated.
Some of them are page caches of superblock of ext4 filesystem.

Current ext4 reads superblock with sb_bread(). sb_bread() 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.

I introduce a new API for allocating page from non-movable area.
It is useful for ext4 and others that want to hold page cache for a long time.

I have 2 patchs:

1. Patch 1/2: introduce a new API that create page cache from non-movable area
2. Patch 2/2: have ext4 use the new API to read superblock

This patchset is based on linux-next-20140717.

Thanks a lot.

Gioh Kim (2):
 fs/buffer.c: allocate buffer cache from non-movable area
 ext4: allocate buffer-cache for superblock in non-movable area

 fs/buffer.c                 |   39 ++++++++++++++++++++++++++++++++-------
 fs/ext4/super.c             |    6 +++---
 include/linux/buffer_head.h |    8 ++++++++
 3 files changed, 43 insertions(+), 10 deletions(-)


             reply	other threads:[~2014-07-22  5:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  5:18 Gioh Kim [this message]
2014-07-22  7:30 ` [PATCH 0/2] new API to allocate buffer-cache for superblock in non-movable area Peter Zijlstra
2014-07-22  8:14   ` Theodore Ts'o
2014-07-27  1:01     ` Theodore Ts'o
2014-07-30  7:56       ` Gioh Kim
2014-07-22  9:38   ` Jan Kara
2014-07-30  7:44     ` Gioh Kim
2014-07-30  7:57       ` Kyungmin Park
2014-07-30 10:11       ` Jan Kara
2014-07-30 10:19         ` Peter Zijlstra
2014-07-30 23:45           ` Gioh Kim
2014-07-30 23:54         ` Gioh Kim
2014-07-31  0:03           ` Jan Kara
2014-07-31  0:37             ` Gioh Kim
2014-07-31 12:21               ` Jan Kara
2014-08-01  0:07                 ` Gioh Kim
2014-08-01  1:06                   ` Gioh Kim
2014-08-01  9:57                     ` Jan Kara
2014-08-01 13:36                       ` Peter Zijlstra
2014-08-01 15:24                         ` Jan Kara
2014-08-01 16:04                           ` Peter Zijlstra
2014-08-06  6:15                             ` Gioh Kim
2014-08-01  8:34                 ` Joonsoo Kim
2014-08-01  9:15                   ` Jan Kara

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=53CDF437.4090306@lge.com \
    --to=gioh.kim@lge.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.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