From: Christoph Lameter <clameter@engr.sgi.com>
To: Lee Schermerhorn <lee.schermerhorn@hp.com>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
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 11:19:58 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602211117570.20413@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1140547791.5207.21.camel@localhost.localdomain>
On Tue, 21 Feb 2006, Lee Schermerhorn wrote:
> 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?
Right. If the kernel configured to not include swap functionality then the
kernel will not include page migration capabilities.
--
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>
prev parent reply other threads:[~2006-02-21 19:19 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
2006-02-21 19:19 ` Christoph Lameter [this message]
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.0602211117570.20413@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=lee.schermerhorn@hp.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