From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Nick Piggin <npiggin@suse.de>
Cc: mingo@elte.hu, cl@linux-foundation.com,
torvalds@linux-foundation.org, mpm@selenic.com,
yinghai@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init: call vfs_caches_init_early() later in the boot sequence
Date: Tue, 2 Jun 2009 09:48:32 +0300 [thread overview]
Message-ID: <84144f020906012348r749f7cfbk3cf7112e6263299b@mail.gmail.com> (raw)
In-Reply-To: <20090601130825.GA1422@wotan.suse.de>
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
next prev parent reply other threads:[~2009-06-02 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 13:29 Pekka Enberg
2009-05-29 1:10 ` Subject: [PATCH] slab: remove bootmem calling Yinghai Lu
2009-06-01 13:10 ` Nick Piggin
2009-05-29 1:12 ` Yinghai Lu
2009-05-29 1:15 ` Yinghai Lu
2009-05-29 1:18 ` Yinghai Lu
2009-05-29 9:07 ` Pekka Enberg
2009-05-29 14:03 ` Christoph Lameter
2009-05-29 8:52 ` Pekka Enberg
2009-06-01 13:08 ` [PATCH] init: call vfs_caches_init_early() later in the boot sequence Nick Piggin
2009-06-02 6:48 ` Pekka Enberg [this message]
2009-06-02 6:55 ` Nick Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84144f020906012348r749f7cfbk3cf7112e6263299b@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=cl@linux-foundation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®