linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <lee.schermerhorn@hp.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] 0/4 Migration Cache Overview
Date: Tue, 21 Feb 2006 13:49:51 -0500	[thread overview]
Message-ID: <1140547791.5207.21.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0602211001110.19955@schroedinger.engr.sgi.com>

On Tue, 2006-02-21 at 10:04 -0800, Christoph Lameter wrote:
> On Tue, 21 Feb 2006, Marcelo Tosatti wrote:
> 
> > The idea was to create a "partition" inside the swapcache which allows
> > for mapping+offset->pfn translation _without_ actually occupying space
> > in the swap map (an idr table is used instead).
> > 
> > But apparently Christoph's mechanism adds the PFN number into
> > the page table entry itself, thus fulfilling the requirement for
> > "mapping+offset"->pfn indexing required for removal of pages underneath
> > a living process. Is that right?
> 
> Right. Swap ptes contain the index into swap space which I am using to 
> preserve the information contained in the pte's of anonymous pages. Thus 
> the existing swap ptes couild be used. There were just a few minor 
> modifications to the swap functions required.
> 

Are the swap ptes used for migrating pages still reserving swap space on
real swap devices?  I thought this was what the migration cache was
trying to avoid.  Now each running instance of direct migration limits
itself to MIGRATE_CHUNK_SIZE [currently] 256 pages, so if the system has
much swap space at all, this shouldn't place too much of a load on swap
space.  But, it does require that one have SOME swap space to migrate,
right?

Lee

--
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:[~2006-02-21 18:49 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
2006-02-21 18:40         ` Marcelo Tosatti
2006-02-21 18:04           ` Christoph Lameter
2006-02-21 18:49             ` Lee Schermerhorn [this message]
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=1140547791.5207.21.camel@localhost.localdomain \
    --to=lee.schermerhorn@hp.com \
    --cc=clameter@engr.sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=nickpiggin@yahoo.com.au \
    /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