From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: NUMA: Patch for node based swapping
Date: Wed, 13 Oct 2004 20:59:48 +1000 [thread overview]
Message-ID: <416D0AA4.30701@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0410121319510.5785@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Tue, 12 Oct 2004, Rik van Riel wrote:
>
>
>>On Tue, 12 Oct 2004, Christoph Lameter wrote:
>>
>>
>>>Any other suggestions?
>>
>>Since this is meant as a stop gap patch, waiting for a real
>>solution, and is only relevant for big (and rare) systems,
>>it would be an idea to at least leave it off by default.
>>
>>I think it would be safe to assume that a $100k system has
>>a system administrator looking after it, while a $5k AMD64
>>whitebox might not have somebody watching its performance.
>
>
> Ok. Will do that then. Should I submit the patch to Andrew?
>
I can't see the harm in sending it after 2.6.9 if it defaults
to off (maybe also make it CONFIG_NUMA).
OTOH, if it is going to be painful to remove later on, then
maybe leave it local to your tree.
It's true that I have something a bit more sophisticated in
the pipe, but it is going to be an uphill battle to get it
and everything it depends on merged - so don't count on it for
2.6.10 :P
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: NUMA: Patch for node based swapping
Date: Wed, 13 Oct 2004 20:59:48 +1000 [thread overview]
Message-ID: <416D0AA4.30701@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0410121319510.5785@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Tue, 12 Oct 2004, Rik van Riel wrote:
>
>
>>On Tue, 12 Oct 2004, Christoph Lameter wrote:
>>
>>
>>>Any other suggestions?
>>
>>Since this is meant as a stop gap patch, waiting for a real
>>solution, and is only relevant for big (and rare) systems,
>>it would be an idea to at least leave it off by default.
>>
>>I think it would be safe to assume that a $100k system has
>>a system administrator looking after it, while a $5k AMD64
>>whitebox might not have somebody watching its performance.
>
>
> Ok. Will do that then. Should I submit the patch to Andrew?
>
I can't see the harm in sending it after 2.6.9 if it defaults
to off (maybe also make it CONFIG_NUMA).
OTOH, if it is going to be painful to remove later on, then
maybe leave it local to your tree.
It's true that I have something a bit more sophisticated in
the pipe, but it is going to be an uphill battle to get it
and everything it depends on merged - so don't count on it for
2.6.10 :P
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-13 11:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 15:02 NUMA: Patch for node based swapping Christoph Lameter
2004-10-12 15:02 ` Christoph Lameter
2004-10-12 15:16 ` Martin J. Bligh
2004-10-12 15:16 ` Martin J. Bligh
2004-10-12 15:38 ` Christoph Lameter
2004-10-12 15:38 ` Christoph Lameter
2004-10-12 15:20 ` Jan-Benedict Glaw
2004-10-12 15:27 ` Rik van Riel
2004-10-12 15:27 ` Rik van Riel
2004-10-12 15:39 ` Christoph Lameter
2004-10-12 15:39 ` Christoph Lameter
2004-10-12 15:52 ` Rik van Riel
2004-10-12 15:52 ` Rik van Riel
2004-10-12 20:20 ` Christoph Lameter
2004-10-12 20:20 ` Christoph Lameter
2004-10-13 10:59 ` Nick Piggin [this message]
2004-10-13 10:59 ` Nick Piggin
2004-10-13 15:14 ` NUMA: Patch for node based swapping V2 Christoph Lameter
2004-10-13 15:14 ` Christoph Lameter
2004-10-12 19:33 ` NUMA: Patch for node based swapping Anton Blanchard
2004-10-12 19:33 ` Anton Blanchard
[not found] <2OwBD-HV-31@gated-at.bofh.it>
[not found] ` <2OwUX-Ua-23@gated-at.bofh.it>
2004-10-12 19:57 ` Andi Kleen
2004-10-12 21:38 ` Ray Bryant
2004-10-12 21:38 ` Ray Bryant
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=416D0AA4.30701@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.