From: Nick Piggin <npiggin@suse.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: mingo@elte.hu, cl@linux-foundation.com,
torvals@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: Mon, 1 Jun 2009 15:08:25 +0200 [thread overview]
Message-ID: <20090601130825.GA1422@wotan.suse.de> (raw)
In-Reply-To: <1243517365.11533.65.camel@penberg-laptop>
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().
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.
> Cc: Christoph Lameter <cl@linux-foundation.com>
> Cc: Linus Torvalds <torvals@linux-foundation.org>
> Cc: Matt Mackall <mpm@selenic.com>
> Cc: Nick Piggin <npiggin@suse.de>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
> fs/dcache.c | 2 +-
> fs/inode.c | 2 +-
> init/main.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/dcache.c b/fs/dcache.c
> index ee60ce4..6c48ba1 100644
> --- a/fs/dcache.c
> +++ b/fs/dcache.c
> @@ -2255,7 +2255,7 @@ static void __init dcache_init_early(void)
> sizeof(struct hlist_head),
> dhash_entries,
> 13,
> - HASH_EARLY,
> + 0,
> &d_hash_shift,
> &d_hash_mask,
> 0);
> diff --git a/fs/inode.c b/fs/inode.c
> index 0571983..92379c8 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -1487,7 +1487,7 @@ void __init inode_init_early(void)
> sizeof(struct hlist_head),
> ihash_entries,
> 14,
> - HASH_EARLY,
> + 0,
> &i_hash_shift,
> &i_hash_mask,
> 0);
> diff --git a/init/main.c b/init/main.c
> index 5a19578..f6bd51f 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -588,7 +588,6 @@ asmlinkage void __init start_kernel(void)
> * kmem_cache_init()
> */
> pidhash_init();
> - vfs_caches_init_early();
> /*
> * Set up kernel memory allocators
> */
> @@ -658,6 +657,7 @@ asmlinkage void __init start_kernel(void)
> initrd_start = 0;
> }
> #endif
> + vfs_caches_init_early();
> cpuset_init_early();
> page_cgroup_init();
> enable_debug_pagealloc();
> --
> 1.6.0.4
>
>
next prev parent reply other threads:[~2009-06-01 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 13:29 [PATCH] init: call vfs_caches_init_early() later in the boot sequence 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 ` Nick Piggin [this message]
2009-06-02 6:48 ` [PATCH] init: call vfs_caches_init_early() later in the boot sequence Pekka Enberg
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=20090601130825.GA1422@wotan.suse.de \
--to=npiggin@suse.de \
--cc=cl@linux-foundation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
--cc=torvals@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