All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Janboe Ye <yuan-bo.ye@motorola.com>,
	linux-kernel@vger.kernel.org, vegard.nossum@gmail.com,
	graydon@redhat.com, fche@redhat.com,
	Nick Piggin <npiggin@suse.de>
Subject: Re: [RFC][PATCH] Check write to slab memory which freed already using mudflap
Date: Fri, 10 Jul 2009 02:04:53 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0907100158090.13880@chino.kir.corp.google.com> (raw)
In-Reply-To: <20090710084745.GA26752@elte.hu>

On Fri, 10 Jul 2009, Ingo Molnar wrote:

> > SLAB is (slowly) going away so you might want to port this to SLUB 
> > as well so we can merge both.
> 
> and SLQB which will replace both? :-/
> 

I'm not sure what the status of slqb is, although I would have expected it 
to have been pushed for inclusion in 2.6.31 as a slab allocator 
alternative.  Nick, any forecast for inclusion?

SLUB has a pretty noticeable performance degradation on benchmarks such as 
netperf TCP_RR with high numbers of threads (see my post about it: 
http://marc.info/?l=linux-kernel&m=123839191416472).  CONFIG_SLAB is the 
optimal configuration for workloads that share similiar slab thrashing 
patterns (which my patchset dealt with in an indirect way and yet still 
didn't match slab's performance).  I haven't yet seen data that suggests 
anything other than CONFIG_SLAB has parity with such a benchmark.

  parent reply	other threads:[~2009-07-10  9:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 16:13 [RFC][PATCH] Check write to slab memory which freed already using mudflap Janboe Ye
2009-07-09 16:44 ` Pekka Enberg
2009-07-09 19:40   ` Janboe Ye
2009-07-10  8:47   ` Ingo Molnar
2009-07-10  8:52     ` Pekka Enberg
2009-07-10  9:03       ` Nick Piggin
2009-07-10  9:14         ` Pekka Enberg
2009-07-10  9:29           ` Nick Piggin
2009-07-10  9:40             ` Pekka Enberg
2009-07-10  9:47               ` David Rientjes
2009-07-10  9:51                 ` Pekka Enberg
2009-07-10 10:03                   ` David Rientjes
2009-07-10 10:10                     ` Pekka Enberg
2009-07-10 10:30                       ` Nick Piggin
2009-07-15 14:59                     ` Nick Piggin
2009-07-15 20:19                       ` David Rientjes
2009-07-20  8:32                         ` Nick Piggin
2009-07-10  9:41             ` David Rientjes
2009-07-10  9:46               ` Pekka Enberg
2009-07-10  9:04     ` David Rientjes [this message]
2009-07-10  9:19       ` Nick Piggin
2009-07-10  9:19       ` Pekka Enberg
2009-07-10  9:31         ` David Rientjes
2009-07-10  9:38           ` Nick Piggin
2009-07-10 18:55             ` 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=alpine.DEB.2.00.0907100158090.13880@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=fche@redhat.com \
    --cc=graydon@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@gmail.com \
    --cc=yuan-bo.ye@motorola.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.