lkml.org 
[lkml]   [2009]   [Jun]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] init: call vfs_caches_init_early() later in the boot sequence
From
Hi Nick,

[ I see I typo'd Linus' email address in the original patch submission... ]

On Thu, May 28, 2009 at 04:29:25PM +0300, Pekka Enberg wrote:
>> From: Pekka Enberg <penberg@cs.helsinki.fi>
>>
>> There's no need to call vfs_caches_init_early() before kmem_cache_init(). All
>> we have to do is make sure we don't attempt to use the bootmem allocator after
>> we've called mem_init().

On Mon, Jun 1, 2009 at 4:08 PM, Nick Piggin <npiggin@suse.de> wrote:
> Hmm, but you'd want to be able to allocate > MAX_ORDER areas in the linear
> KVA, which the page allocator cannot do. So this is just going to silently
> truncate hash table size. Nack on this one.

OK, makes sense. IIRC, Linus suggested doing this but I think I'll
just revert the patch.

Pekka


\
 
 \ /
  Last update: 2009-06-02 08:51    [W:0.598 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site