From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Lee Schermerhorn <lee.schermerhorn@hp.com>,
linux-mm <linux-mm@kvack.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: [RFC] 0/4 Migration Cache Overview
Date: Tue, 21 Feb 2006 14:18:40 +1100 [thread overview]
Message-ID: <43FA8690.3070608@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0602170906030.31408@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Fri, 17 Feb 2006, Lee Schermerhorn wrote:
>
>
>>>Could add a justification of this feature? What is the benefit of having a
>>>migration cache instead of using swap pte (current migration is not really
>>>using swap space per se)?
>>
>>I think Marcello covered that in his original posts, which I linked.
>>I can go back and extract his arguments. My primary interest is for
>>"lazy page migration" where anon pages can hang around the the cache
>>until the task faults them in [possibly migrating] or exits, if ever.
>>I think the desire to avoid using swap for this case is even stronger.
>
>
> I am bit confused. A task faults in a page from the migration cache? Isnt
> this swap behavior? I thought the migration cache was just to avoid using
> swap page numbers for the intermediate pte values during migration?
>
It really does seem like the swapcache does everything required. The
swapcache is just a pagecache mapping for anonymous pages. Adding an
extra "somethingcache" for anonymous pages shouldn't add anything. I
guess I'm missing something as well.
> You are moving the page when it is faulted in?
>
> Including Marcelo's rationale may help understanding here. I read it a
> while back but I do not remember the details. Please give us an overview.
>
Yes, this should always be done in patches themselves rather than
linking to other posts (within reason), because it gives you something
to reply to and it gets into the changeset history.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.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>
next prev parent reply other threads:[~2006-02-21 3:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 15:36 Lee Schermerhorn
2006-02-17 16:22 ` Christoph Lameter
2006-02-17 16:59 ` Lee Schermerhorn
2006-02-17 17:12 ` Christoph Lameter
2006-02-21 3:18 ` Nick Piggin [this message]
2006-02-21 18:40 ` Marcelo Tosatti
2006-02-21 18:04 ` Christoph Lameter
2006-02-21 18:49 ` Lee Schermerhorn
2006-02-21 19:19 ` 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=43FA8690.3070608@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=clameter@engr.sgi.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.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