From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 11 Jul 2005 11:02:26 -0700 (PDT) From: Christoph Lameter Subject: Re: [NUMA] /proc//numa_maps to show on which nodes pages reside In-Reply-To: <1121102433.15095.26.camel@localhost> Message-ID: References: <1121102433.15095.26.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Dave Hansen Cc: linux-mm , ia64 list , pj@sgi.com List-ID: On Mon, 11 Jul 2005, Dave Hansen wrote: > So, if something like numa_maps existed, but pointed to the memory > object instead of the NUMA node directly, you could still easily derive > the NUMA node. But, you'd also get information about which particular > bits of memory are being used. That might be useful for a user that's > getting desperate to remove some memory and wants to kill some processes > that might be less than willing to release that memory. We really need both I guess. If you dealing with a batch scheduler that wants to move memory around between nodes in order to optimize programs then you nedd to have numa_maps. Maybe we need to have two: numa_maps and memory_maps? > The downside is that we'll have to get that sysfs stuff working for ! > SPARSEMEM configurations. If we have two maps then we can avoid that. -- 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: aart@kvack.org