From: Christoph Lameter <clameter@sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, mel@csn.ul.ie, y-goto@jp.fujitsu.com,
hugh@veritas.com
Subject: Re: memory unplug v4 intro [1/6] migration without mm->sem
Date: Fri, 8 Jun 2007 00:21:39 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706080019400.29461@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070608160148.616dae54.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 8 Jun 2007, KAMEZAWA Hiroyuki wrote:
> On Thu, 7 Jun 2007 23:44:38 -0700 (PDT)
> Christoph Lameter <clameter@sgi.com> wrote:
>
> > I think what Hugh meant is someething like this:
> >
> Hmm, I see.
>
>
> > /*
> > + * Add dummy vma so that the vma cannot vanish under us
> > + */
> > + if (PageAnon(page))
> > + anon_vma_link(&dummy_vma);
> > +
> Before calling anon_vma_link(), I have to set "dummy_vma->anon_vma = anon_vma".
> anon_vma_hold() does what it has to do.
Yup. Forgot that one.
> But it's not necessary to add anon_vma_hold() in rmap.c, as you pointed out.
> I'll rewrite them as static func in migrate.c
I do not think you need anon_vma_hold at all. Neither do you need to add
any other function. The presence of the dummy vma while the page is
removed and added guarantees that it does not vanish.
--
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>
next prev parent reply other threads:[~2007-06-08 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 5:35 memory unplug v4 intro [0/6] KAMEZAWA Hiroyuki
2007-06-08 5:38 ` memory unplug v4 intro [1/6] migration without mm->sem KAMEZAWA Hiroyuki
2007-06-08 5:47 ` Christoph Lameter
2007-06-08 5:54 ` KAMEZAWA Hiroyuki
2007-06-08 5:57 ` Christoph Lameter
2007-06-08 6:06 ` KAMEZAWA Hiroyuki
2007-06-08 6:44 ` Christoph Lameter
2007-06-08 7:01 ` KAMEZAWA Hiroyuki
2007-06-08 7:21 ` Christoph Lameter [this message]
2007-06-08 7:25 ` KAMEZAWA Hiroyuki
2007-06-08 5:39 ` memory unplug v4 [2/6] lru isolation race fix KAMEZAWA Hiroyuki
2007-06-08 5:52 ` Christoph Lameter
2007-06-08 5:58 ` KAMEZAWA Hiroyuki
2007-06-08 5:58 ` Christoph Lameter
2007-06-08 5:40 ` memory unplug v4 intro [3/6] walk memory resources KAMEZAWA Hiroyuki
2007-06-08 5:41 ` memory unplug v4 intro [4/6] page isolation KAMEZAWA Hiroyuki
2007-06-08 13:24 ` Mel Gorman
2007-06-08 13:59 ` KAMEZAWA Hiroyuki
2007-06-08 5:43 ` memory unplug v4 intro [5/6] page offlining KAMEZAWA Hiroyuki
2007-06-08 5:43 ` memory unplug v4 intro [6/6] ia64 interface KAMEZAWA Hiroyuki
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=Pine.LNX.4.64.0706080019400.29461@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=y-goto@jp.fujitsu.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