linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, linux-mm@kvack.org, ak@suse.de,
	lhms-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/2] Page migration via Swap V2: Overview
Date: Tue, 18 Oct 2005 10:16:42 -0200	[thread overview]
Message-ID: <20051018121642.GA13963@logos.cnet> (raw)
In-Reply-To: <20051018004932.3191.30603.sendpatchset@schroedinger.engr.sgi.com>

On Mon, Oct 17, 2005 at 05:49:32PM -0700, Christoph Lameter wrote:
> In a NUMA system it is often beneficial to be able to move the memory
> in use by a process to different nodes in order to enhance performance.
> Currently Linux simply does not support this facility.
> 
> Page migration is also useful for other purposes:
> 
> 1. Memory hotplug. Migrating processes off a memory node that is going
>    to be disconnected.
> 
> 2. Remapping of bad pages. These could be detected through soft ECC errors
>    and other mechanisms.
> 
> Work on page migration has been done in the context of the memory hotplug project
> (see https://lists.sourceforge.net/lists/listinfo/lhms-devel). Ray Bryant
> hs also posted a series of manual page migration patchsets. However, the patches
> are complex, and may have impacts on the VM in various places, there are unresolved
> issues regarding memory placement during direct migration and thus the functionality
> may not be available for some time.

Is there a description of the unresolved issues you mention somewhere?

Having a duplicate implementation is somewhat disappointing - why not fix the problems
with real page migration?

> This patchset was done in awareness of the work done there and realizes page
> migration via swap. Pages are not directly moved to their target
> location but simply swapped out. If the application touches the page later then
> a new page is allocated in the desired location.
> 
> The advantage of page based swapping is that the necessary changes to the kernel
> are minimal. With a fully functional but minimal page migration capability we
> will be able to enhance low level code and higher level APIs at the same time.

> This will hopefully decrease the time needed to get the code for direct page
> migration working and into the kernel trees.

Why would that be the case?

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

  parent reply	other threads:[~2005-10-18 12:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  0:49 Christoph Lameter
2005-10-18  0:49 ` [PATCH 1/2] Page migration via Swap V2: Page Eviction Christoph Lameter
2005-10-18  1:04   ` Andrew Morton
2005-10-18  8:51     ` Nick Piggin
2005-10-18 16:38     ` Christoph Lameter
2005-10-18  8:34   ` Magnus Damm
2005-10-18 16:43     ` Christoph Lameter
2005-10-19 10:04       ` Magnus Damm
2005-10-19 15:29         ` Christoph Lameter
2005-10-19 20:32         ` Christoph Lameter
2005-10-18  0:49 ` [PATCH 2/2] Page migration via Swap V2: MPOL_MF_MOVE interface Christoph Lameter
2005-10-18 10:05   ` Magnus Damm
2005-10-18 16:46     ` Christoph Lameter
2005-10-18  3:18 ` [PATCH 0/2] Page migration via Swap V2: Overview KAMEZAWA Hiroyuki
2005-10-18 14:27   ` [Lhms-devel] " Lee Schermerhorn
2005-10-18 16:47   ` Christoph Lameter
2005-10-18  6:37 ` KAMEZAWA Hiroyuki
2005-10-18 16:50   ` Christoph Lameter
2005-10-18 12:16 ` Marcelo Tosatti [this message]
2005-10-18 16:54   ` 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=20051018121642.GA13963@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-mm@kvack.org \
    /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