From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Benjamin LaHaise <bcrl@kvack.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
tangchen <tangchen@cn.fujitsu.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 0/2] Add support to aio ring pages migration
Date: Thu, 11 Jul 2013 18:11:28 +0800 [thread overview]
Message-ID: <51DE84D0.2000209@cn.fujitsu.com> (raw)
In-Reply-To: <51DA96BC.1060701@cn.fujitsu.com>
ping...
On 07/08/2013 06:38 PM, Gu Zheng wrote:
> Currently aio ring pages use get_user_pages() to allocate pages from movable
> zone,as discussed in thread https://lkml.org/lkml/2012/11/29/69, it is easy to
> pin user pages for a long time, which is fatal for memory hotplug/remove framework.
>
> As Mel Gorman suggested, "Implement a callback for migration to unpin pages,
> barrier operations until migration completes and pin the new pfns" can soloved
> this issue. And the best palce to hold the callbacks is address space operations
> which can be found via page->mapping.
>
> But the current aio ring pages are anonymous pages, they don't have
> address_space_operations, so we use an anon inode file as the aio ring file to
> manage the aio ring pages, so that we can implement the callback and register it
> to page->mmapping->a_ops->migratepage.
>
> But there's a ploblem that all files created by anon_inode_getfile() share the
> same inode, so mutil aio context will share the same aio ring pages, it'll lead
> to io events chaos. In order to solve this issus, we introduce a new fucntion
> anon_inode_getfile_private() which is samilar to anon_inode_getfile(), but each
> new file has its own anon inode.
>
> This work is based on Benjamin's patch,
> http://www.spinics.net/lists/linux-fsdevel/msg66014.html
>
> Gu Zheng (2):
> fs/anon_inode: Introduce a new lib function
> anon_inode_getfile_private()
> fs/aio: Add support to aio ring pages migration
>
> fs/aio.c | 120 +++++++++++++++++++++++++++++++++++++++----
> fs/anon_inodes.c | 66 +++++++++++++++++++++++
> include/linux/anon_inodes.h | 3 +
> include/linux/migrate.h | 3 +
> mm/migrate.c | 2 +-
> 5 files changed, 182 insertions(+), 12 deletions(-)
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Benjamin LaHaise <bcrl@kvack.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
tangchen <tangchen@cn.fujitsu.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 0/2] Add support to aio ring pages migration
Date: Thu, 11 Jul 2013 18:11:28 +0800 [thread overview]
Message-ID: <51DE84D0.2000209@cn.fujitsu.com> (raw)
In-Reply-To: <51DA96BC.1060701@cn.fujitsu.com>
ping...
On 07/08/2013 06:38 PM, Gu Zheng wrote:
> Currently aio ring pages use get_user_pages() to allocate pages from movable
> zone,as discussed in thread https://lkml.org/lkml/2012/11/29/69, it is easy to
> pin user pages for a long time, which is fatal for memory hotplug/remove framework.
>
> As Mel Gorman suggested, "Implement a callback for migration to unpin pages,
> barrier operations until migration completes and pin the new pfns" can soloved
> this issue. And the best palce to hold the callbacks is address space operations
> which can be found via page->mapping.
>
> But the current aio ring pages are anonymous pages, they don't have
> address_space_operations, so we use an anon inode file as the aio ring file to
> manage the aio ring pages, so that we can implement the callback and register it
> to page->mmapping->a_ops->migratepage.
>
> But there's a ploblem that all files created by anon_inode_getfile() share the
> same inode, so mutil aio context will share the same aio ring pages, it'll lead
> to io events chaos. In order to solve this issus, we introduce a new fucntion
> anon_inode_getfile_private() which is samilar to anon_inode_getfile(), but each
> new file has its own anon inode.
>
> This work is based on Benjamin's patch,
> http://www.spinics.net/lists/linux-fsdevel/msg66014.html
>
> Gu Zheng (2):
> fs/anon_inode: Introduce a new lib function
> anon_inode_getfile_private()
> fs/aio: Add support to aio ring pages migration
>
> fs/aio.c | 120 +++++++++++++++++++++++++++++++++++++++----
> fs/anon_inodes.c | 66 +++++++++++++++++++++++
> include/linux/anon_inodes.h | 3 +
> include/linux/migrate.h | 3 +
> mm/migrate.c | 2 +-
> 5 files changed, 182 insertions(+), 12 deletions(-)
>
next prev parent reply other threads:[~2013-07-11 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 10:38 [PATCH 0/2] Add support to aio ring pages migration Gu Zheng
2013-07-08 10:38 ` Gu Zheng
2013-07-11 10:11 ` Gu Zheng [this message]
2013-07-11 10:11 ` Gu Zheng
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=51DE84D0.2000209@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=tangchen@cn.fujitsu.com \
--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.