From: Theodore Ts'o <tytso@mit.edu>
To: Gioh Kim <gioh.kim@lge.com>
Cc: akpm@linux-foundation.org, jack@suse.cz,
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, minchan@kernel.org, js1304@gmail.com,
gunho.lee@lge.com
Subject: Re: [PATCHv4 2/3] ext4: use non-movable memory for the ext4 superblock
Date: Thu, 4 Sep 2014 22:37:36 -0400 [thread overview]
Message-ID: <20140905023736.GB1971@thunk.org> (raw)
In-Reply-To: <1409815781-28011-3-git-send-email-gioh.kim@lge.com>
On Thu, Sep 04, 2014 at 04:29:40PM +0900, Gioh Kim wrote:
> A buffer-cache for superblock is disturbing page migration,
> because the buffer-cache is not released until unmount.
> The buffer-cache must be allocated from non-movable area.
>
> Signed-off-by: Gioh Kim <gioh.kim@lge.com>
> Reviewed-by: Jan Kara <jack@suse.cz>
Thanks, I've applied this to the ext4 git tree with a slightly
rewritten commit description (for clarity).
- Ted
next prev parent reply other threads:[~2014-09-05 2:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 7:29 [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag Gioh Kim
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 [this message]
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=20140905023736.GB1971@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=gioh.kim@lge.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.