linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Christoph Lameter <cl@gentwo.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	k.kozlowski@samsung.com,
	Seth Jennings <sjenning@linux.vnet.ibm.com>,
	Mel Gorman <mgorman@suse.de>,
	guz.fnst@cn.fujitsu.com, Benjamin LaHaise <bcrl@kvack.org>,
	Dave Hansen <dave.hansen@intel.com>,
	lliubbo@gmail.com, aquini@redhat.com,
	Rik van Riel <riel@redhat.com>
Subject: Re: [RFC 0/3] Pin page control subsystem
Date: Wed, 14 Aug 2013 09:12:37 +0900	[thread overview]
Message-ID: <20130814001236.GC2271@bbox> (raw)
In-Reply-To: <00000140787b6191-ae3f2eb1-515e-48a1-8e64-502772af4700-000000@email.amazonses.com>

Hello Christoph,

On Tue, Aug 13, 2013 at 04:21:30PM +0000, Christoph Lameter wrote:
> On Tue, 13 Aug 2013, Minchan Kim wrote:
> 
> > VM sometime want to migrate and/or reclaim pages for CMA, memory-hotplug,
> > THP and so on but at the moment, it could handle only userspace pages
> > so if above example subsystem have pinned a some page in a range VM want
> > to migrate, migration is failed so above exmaple couldn't work well.
> 
> Dont we have the mmu_notifiers that could help in that case? You could get
> a callback which could prepare the pages for migration?

Now I'm not familiar with mmu_notifier so please could you elaborate it
a bit for me to dive into that? 

Thanks!

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

-- 
Kind regards,
Minchan Kim

--
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:[~2013-08-14  0:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  7:04 [RFC 0/3] Pin page control subsystem Minchan Kim
2013-08-13  7:05 ` [RFC 1/3] mm: Introduce new page flag Minchan Kim
2013-08-13  7:05 ` [RFC 2/3] pinpage control subsystem Minchan Kim
2013-08-13  7:05 ` [RFC 3/3] mm: migrate pinned page Minchan Kim
2013-08-13  9:46 ` [RFC 0/3] Pin page control subsystem Krzysztof Kozlowski
2013-08-13 14:23   ` Benjamin LaHaise
2013-08-14  0:08     ` Minchan Kim
2013-08-13 23:54   ` Minchan Kim
2013-08-13 16:21 ` Christoph Lameter
2013-08-14  0:12   ` Minchan Kim [this message]
2013-08-14 16:36     ` Christoph Lameter
2013-08-14 16:47       ` Minchan Kim
2013-08-14 16:58         ` Christoph Lameter
2013-08-15  4:48           ` Minchan Kim
2013-08-15 15:18             ` Christoph Lameter

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=20130814001236.GC2271@bbox \
    --to=minchan@kernel.org \
    --cc=aquini@redhat.com \
    --cc=bcrl@kvack.org \
    --cc=cl@gentwo.org \
    --cc=dave.hansen@intel.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=mgorman@suse.de \
    --cc=riel@redhat.com \
    --cc=sjenning@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).