From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andi Kleen <andi@firstfloor.org>
Subject: Re: Off topic: Numactl "distance" wrong
Cc: kosaki.motohiro@jp.fujitsu.com, Yinghai Lu <yhlu.kernel@gmail.com>,
       David Rientjes <rientjes@google.com>, Chris Worley <worleys@gmail.com>,
       linux-kernel@vger.kernel.org
In-Reply-To: <87r609jtc2.fsf@basil.nowhere.org>
References: <86802c440904031448yc6d499ckd9cb969ce136f477@mail.gmail.com> <87r609jtc2.fsf@basil.nowhere.org>
Message-Id: <20090407111539.F0F5.A69D9226@jp.fujitsu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue,  7 Apr 2009 11:52:56 +0900 (JST)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 769
Lines: 23

> That's not enough. You would need to redo all the zone fallback tables
> in the VM that are initialized based on topology, do new scheduler
> topologies and all kind of other stuff.

I think this is very good viewpoint.

The rebuilding zone fallback table and scheduler topologies need to add
new lock.

Oh well, who need memory and scheduler performance regression?
Then, its /sys interface isn't so useful.


I don't think the manual setting of node distance improve
opteron's (or another small machine) performance.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/