linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lin Feng <linfeng@cn.fujitsu.com>
To: Zach Brown <zab@zabbo.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	viro@zeniv.linux.org.uk, bcrl@kvack.org,
	kamezawa.hiroyu@jp.fujitsu.com, mhocko@suse.cz, hughd@google.com,
	cl@linux.com, mgorman@suse.de, minchan@kernel.org,
	isimatu.yasuaki@jp.fujitsu.com, laijs@cn.fujitsu.com,
	wency@cn.fujitsu.com, tangchen@cn.fujitsu.com,
	linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG REPORT] [mm-hotplug, aio] aio ring_pages can't be offlined
Date: Fri, 30 Nov 2012 11:39:40 +0800	[thread overview]
Message-ID: <50B82A7C.8020202@cn.fujitsu.com> (raw)
In-Reply-To: <20121130000443.GK18574@lenny.home.zabbo.net>

Hi Zach,

Thanks for your advice. So agree, I will look into it to lead aio 
to use non-movable pages.


Thanks,
linfeng
On 11/30/2012 08:04 AM, Zach Brown wrote:
>> The best I can think of is to make changes in or around
>> get_user_pages(), to steal the pages from userspace and replace them
>> with non-movable ones before pinning them.  The performance cost of
>> something like this would surely be unacceptable for direct-io, but
>> maybe OK for the aio ring and futexes.
> 
> In the aio case it seems like it could be taught to populate the mapping
> with non-movable pages to begin with.  It's calling get_user_pages() a
> few lines after instantiating the mapping itself with do_mmap_pgoff().
> 
> - z
> 

-- 
--------------------------------------------------
Lin Feng
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road,
Nanjing, 210012, China
PHONE:+86-25-86630566-8557 
COINS:7998-8557 
FAX:+86-25-83317685
MAIL:linfeng@cn.fujitsu.com
--------------------------------------------------

--
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>

  reply	other threads:[~2012-11-30  3:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29  6:54 Lin Feng
2012-11-29 23:39 ` Andrew Morton
2012-11-30  0:04   ` Zach Brown
2012-11-30  3:39     ` Lin Feng [this message]
2012-11-30  3:42   ` Lin Feng
2012-11-30  5:57     ` Andrew Morton
2012-11-30  7:01       ` Lin Feng
2012-11-30  7:55         ` Andrew Morton
2012-11-30 10:29           ` Lin Feng
2012-11-30 10:47             ` Andrew Morton
2012-12-03  3:00               ` Lin Feng
2012-11-30 11:00           ` Mel Gorman
2012-12-03  2:52             ` Lin Feng
2012-12-03 11:37               ` Mel Gorman
2012-11-30  7:13       ` Kamezawa Hiroyuki
2012-11-30  8:00         ` Andrew Morton
2012-11-30 10:57   ` Mel Gorman
2012-11-30 15:24 ` Domenico Andreoli
2012-12-03  2:05   ` Lin Feng

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=50B82A7C.8020202@cn.fujitsu.com \
    --to=linfeng@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=bcrl@kvack.org \
    --cc=cl@linux.com \
    --cc=hughd@google.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.cz \
    --cc=minchan@kernel.org \
    --cc=tangchen@cn.fujitsu.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wency@cn.fujitsu.com \
    --cc=zab@zabbo.net \
    /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