From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 1 Nov 2006 16:27:26 -0800 (PST) From: Christoph Lameter Subject: Re: Page allocator: Single Zone optimizations In-Reply-To: <20061101162221.f110b56a.akpm@osdl.org> Message-ID: References: <20061027190452.6ff86cae.akpm@osdl.org> <20061027192429.42bb4be4.akpm@osdl.org> <20061027214324.4f80e992.akpm@osdl.org> <20061028180402.7c3e6ad8.akpm@osdl.org> <4544914F.3000502@yahoo.com.au> <20061101182605.GC27386@skynet.ie> <20061101123451.3fd6cfa4.akpm@osdl.org> <20061101162221.f110b56a.akpm@osdl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Andrew Morton Cc: Mel Gorman , Mel Gorman , Nick Piggin , KAMEZAWA Hiroyuki , linux-mm@kvack.org List-ID: On Wed, 1 Nov 2006, Andrew Morton wrote: > > I think that choice is better than fiddling with the VM by adding > > additional zones which will introduce lots of other problems. > > What lots of other problems? 64x64MB zones works good. Read my earlier mail on this. Certainly you can make this work for a specialized load that does not use all kernel features. > > Right. So the device needs to disengage and then move its structures. > > I don't think we have a snowball's chance of making all kernel memory > relocatable. Or even a useful amount of it. In the simplest case the device would close down free all of its memory and then start up again reallocating necessary memory? -- 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: email@kvack.org