linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <christoph@lameter.com>
Cc: Andi Kleen <ak@suse.de>, Paul Jackson <pj@sgi.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: NUMA policy interface
Date: Fri, 5 Aug 2005 11:16:30 +0200	[thread overview]
Message-ID: <20050805091630.GL8266@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508041642130.15157@graphe.net>

On Thu, Aug 04, 2005 at 04:49:33PM -0700, Christoph Lameter wrote:
> On Fri, 5 Aug 2005, Andi Kleen wrote:
> 
> > None of them seem very attractive to me.  I would prefer to just
> > not support external accesses keeping things lean and fast.
> 
> That is a surprising statement given what we just discussed. Things 
> are not lean and fast but weirdly screwed up. The policy layer is 
> significantly impacted by historical contingencies rather than designed in 
> a clean way. It cannot even deliver the functionality it was designed to 
> deliver (see BIND).

That seems like a unfair description to me. While things are not
perfect they are definitely not as bad as you're trying to paint them.

> 
> > Individual physical page migration is quite different from
> > address space migration.
> 
> Address space migration? That is something new in this discussion. So 
> could you explain what you mean by that? I have looked at page migration 
> in a variety of contexts and could not see much difference.

MCE page migration just puts a physical page to somewhere else.
memory hotplug migration does the same for multiple pages from
different processes.

Page migration like you're asking for migrates whole processes.

-Andi

--
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:[~2005-08-05  9:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050730181418.65caed1f.pj@sgi.com>
     [not found] ` <Pine.LNX.4.62.0507301814540.31359@graphe.net>
     [not found]   ` <20050730190126.6bec9186.pj@sgi.com>
     [not found]     ` <Pine.LNX.4.62.0507301904420.31882@graphe.net>
     [not found]       ` <20050730191228.15b71533.pj@sgi.com>
     [not found]         ` <Pine.LNX.4.62.0508011147030.5541@graphe.net>
     [not found]           ` <20050803084849.GB10895@wotan.suse.de>
     [not found]             ` <Pine.LNX.4.62.0508040704590.3319@graphe.net>
     [not found]               ` <20050804142942.GY8266@wotan.suse.de>
     [not found]                 ` <Pine.LNX.4.62.0508040922110.6650@graphe.net>
     [not found]                   ` <20050804170803.GB8266@wotan.suse.de>
2005-08-04 17:34                     ` Christoph Lameter
2005-08-04 21:14                       ` Andi Kleen
2005-08-04 21:21                         ` Christoph Lameter
2005-08-04 21:41                           ` Andi Kleen
2005-08-04 22:19                             ` Christoph Lameter
2005-08-04 22:44                               ` Mike Kravetz
2005-08-04 23:40                               ` Andi Kleen
2005-08-04 23:49                                 ` Christoph Lameter
2005-08-05  9:16                                   ` Andi Kleen [this message]
2005-08-05 14:52                                     ` Christoph Lameter
2005-08-05 14:58                                     ` 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=20050805091630.GL8266@wotan.suse.de \
    --to=ak@suse.de \
    --cc=christoph@lameter.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.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