linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	mingo@elte.hu
Subject: Re: slab: setup allocators earlier in the boot sequence
Date: Fri, 12 Jun 2009 11:17:28 +0300	[thread overview]
Message-ID: <1244794648.30512.21.camel@penberg-laptop> (raw)
In-Reply-To: <1244792380.7172.77.camel@pasglop>

Hi Ben,

On Fri, 2009-06-12 at 17:39 +1000, Benjamin Herrenschmidt wrote:
> For example, slab_is_available() didn't always exist, and so in the
> early days on powerpc, we used a mem_init_done global that is set form
> mem_init() (not perfect but works in practice). And we still have code
> using that to do the test.

Looking at powerpc arch code, can we get rid of the *_maybe_bootmem()
functions now? Or is slab initialization too late still? FWIW, I think
one simple fix on PPC is to just clear __GFP_NOWAIT in those functions
(all of them seem to be using GFP_KERNEL which is wrong during boot).

			Pekka

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2009-06-12  8:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200906111959.n5BJxFj9021205@hera.kernel.org>
     [not found] ` <1244770230.7172.4.camel@pasglop>
     [not found]   ` <1244779009.7172.52.camel@pasglop>
     [not found]     ` <1244780756.7172.58.camel@pasglop>
2009-06-12  5:07       ` Benjamin Herrenschmidt
2009-06-12  6:16         ` Pekka J Enberg
2009-06-12  7:34           ` Benjamin Herrenschmidt
2009-06-12  7:39             ` Benjamin Herrenschmidt
2009-06-12  7:47               ` Pekka Enberg
2009-06-12  8:17               ` Pekka Enberg [this message]
2009-06-12  8:47                 ` Benjamin Herrenschmidt
2009-06-12  7:45             ` Pekka Enberg
2009-06-12  7:54               ` Nick Piggin
2009-06-12  7:59                 ` Pekka Enberg
2009-06-12  8:02                   ` Nick Piggin
2009-06-12  8:04                     ` Pekka Enberg
2009-06-12  8:20                       ` Nick Piggin
2009-06-12  8:44                       ` Benjamin Herrenschmidt
2009-06-12  8:49                         ` Pekka Enberg
2009-06-12  9:13                           ` Nick Piggin
2009-06-12  9:24                             ` Benjamin Herrenschmidt
2009-06-12  9:30                               ` Nick Piggin
2009-06-12  9:44                                 ` Benjamin Herrenschmidt
2009-06-12  9:49                                   ` Nick Piggin
2009-06-12  8:44                     ` Benjamin Herrenschmidt
2009-06-12  8:42                 ` Benjamin Herrenschmidt
2009-06-12  8:40               ` Benjamin Herrenschmidt
2009-06-12  8:43                 ` Pekka Enberg
2009-06-12  8:53                   ` Benjamin Herrenschmidt
2009-06-12  9:05                     ` Pekka Enberg
2009-06-12  9:14                       ` Nick Piggin
2009-06-12  9:07                     ` Pekka Enberg
2009-06-12 13:49                       ` Christoph Lameter
2009-06-12 13:54                         ` Pekka Enberg
2009-06-12 14:02                           ` Benjamin Herrenschmidt
2009-06-12 14:04                             ` Pekka Enberg
2009-06-12 14:07                           ` Christoph Lameter
2009-06-12 14:00                         ` Benjamin Herrenschmidt
2009-06-12 13:44                   ` Christoph Lameter

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=1244794648.30512.21.camel@penberg-laptop \
    --to=penberg@cs.helsinki.fi \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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