All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Nick Piggin <npiggin@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [rfc][patch] slob: improvements
Date: Fri, 13 Jul 2007 13:35:06 -0500	[thread overview]
Message-ID: <20070713183506.GN11115@waste.org> (raw)
In-Reply-To: <20070713112725.d75acf1d.randy.dunlap@oracle.com>

On Fri, Jul 13, 2007 at 11:27:25AM -0700, Randy Dunlap wrote:
> > Index: linux-2.6/init/Kconfig
> > ===================================================================
> > --- linux-2.6.orig/init/Kconfig
> > +++ linux-2.6/init/Kconfig
> > @@ -529,7 +529,7 @@ config SLUB
> >  	   way and has enhanced diagnostics.
> >  
> >  config SLOB
> > -	depends on EMBEDDED && !SPARSEMEM
> > +	depends on EMBEDDED && !SPARSEMEM && !ARCH_USES_SLAB_PAGE_STRUCT
> >  	bool "SLOB (Simple Allocator)"
> >  	help
> >  	   SLOB replaces the SLAB allocator with a drastically simpler
> 
> Is this patch going in?  I have a randconfig (2.6.22) with
> CONFIG_SLOB=y
> CONFIG_NUMA=y
> CONFIG_SMP=y
> The kernel build fails with these config symbols set like that.
> It looks like SLOB needs that additional
> 	&& !ARCH_USES_SLAB_PAGE_STRUCT
> (or 	&& !SMP)

I think Andrew intends to push it to 2.6.23, yes.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-07-13 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15  8:43 [rfc][patch] slob: improvements Nick Piggin
2007-05-15 15:17 ` Matt Mackall
2007-05-15 23:33   ` Nick Piggin
2007-07-13 18:27     ` Randy Dunlap
2007-07-13 18:35       ` Matt Mackall [this message]
2007-07-13 18:45         ` Andrew Morton

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=20070713183506.GN11115@waste.org \
    --to=mpm@selenic.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=randy.dunlap@oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.