mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: NUMA mempolicy /proc code in mainline shouldn't have been merged
Date: Mon, 19 Sep 2005 21:40:45 +0200	[thread overview]
Message-ID: <20050919194038.GB12810@verdi.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0509190958470.25549@schroedinger.engr.sgi.com>

On Mon, Sep 19, 2005 at 10:11:20AM -0700, Christoph Lameter wrote:
> However, one still does not know which memory section (vma) is allocated 
> on which nodes. And this may be important since critical data may need to 

Maybe. Well sure of things could be maybe important. Or maybe not.
Doesn't seem like a particularly strong case to add a lot of ugly
code though.

> External memory policy management is a necessary feature for system 
> administration, batch process scheduling as well as for testing and 
> debugging a system.

I'm not convinced of this at all. Most of these things proposed so far
can be done much simpler with 90% of the functionality (e.g. just swapoff
per process for migration) , and I haven't seen a clear rationale except
for lots of maybes that the missing 10% are worth all the complexity
you seem to plan to add.

-Andi

  reply	other threads:[~2005-09-19 19:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10  9:20 Andi Kleen
2005-09-10  9:33 ` Andrew Morton
2005-09-10 16:29   ` Christoph Lameter
2005-09-11  0:59     ` Andrew Morton
2005-09-11  2:46       ` Christoph Lameter
2005-09-11  6:51         ` Andrew Morton
2005-09-11  7:11           ` Andi Kleen
2005-09-19 17:11             ` Christoph Lameter
2005-09-19 19:40               ` Andi Kleen [this message]
2005-09-19 21:32                 ` Christoph Lameter
2005-09-19 21:56                   ` Andi Kleen
2005-09-19 22:48                     ` Andrew Morton
2005-09-19 23:13                       ` Christoph Lameter
2005-09-25  1:45                         ` Paul Jackson

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=20050919194038.GB12810@verdi.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®