Re: [patch -mm 3/5] x86_64: fixed-size remaining fake nodes

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Andi Kleen <ak@...>
Cc: Andrew Morton <akpm@...>, Rohit Seth <rohitseth@...>, <linux-kernel@...>
Date: Monday, January 29, 2007 - 2:38 pm

On Mon, 29 Jan 2007, Andi Kleen wrote:


The only other appropriate syntax that comes to mind is perhaps a 
command-line that ends with a 0.  For example, numa=fake=2*512,0 would 
allocate two 512M nodes and nothing for the remaining RAM.


There are.  Configurable node sizes (i.e. 'numa=fake=512,4*128', etc) are 
the major concept and help to avoid the overhead associated with something 
like 64 nodes of 64M each on a 4G machine.  We've seen some inefficiencies 
with scanning through so many zone lists on page_alloc when we encounter a 
full node.  Additional support such as 'numa=fake=2*512,*128' are used 
more for machines where you're unsure of their total system RAM in the 
first place but want to make sure you have the node sizes you need.

		David
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch -mm 1/5] x86_64: configurable fake numa node sizes, David Rientjes, (Thu Jan 25, 5:37 pm)
[patch -mm 2/5] x86_64: split remaining fake nodes equally, David Rientjes, (Thu Jan 25, 5:37 pm)
[patch -mm 3/5] x86_64: fixed-size remaining fake nodes, David Rientjes, (Thu Jan 25, 5:37 pm)
Re: [patch -mm 3/5] x86_64: fixed-size remaining fake nodes, David Rientjes, (Mon Jan 29, 2:38 pm)
[patch -mm 4/5] x86_64: fake numa function annotations, David Rientjes, (Thu Jan 25, 5:37 pm)