From: Christoph Lameter <cl@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: David Rientjes <rientjes@google.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>, Janboe Ye <yuan-bo.ye@motorola.com>,
linux-kernel@vger.kernel.org, vegard.nossum@gmail.com,
graydon@redhat.com, fche@redhat.com
Subject: Re: [RFC][PATCH] Check write to slab memory which freed already using mudflap
Date: Fri, 10 Jul 2009 14:55:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0907101453240.14152@gentwo.org> (raw)
In-Reply-To: <20090710093825.GJ14666@wotan.suse.de>
On Fri, 10 Jul 2009, Nick Piggin wrote:
> Don't know whether it should go in as non-default or not. The plan
> is to kind of kick up a stink and make people care about the slab
> issue again rather than quietly add more slab allocators to the
> tree...
>
> Perhaps making it non-default for one release would be a good idea,
> I don't know.
Just merging it as non default could be done now as far as I can tell.
Then there may be more people working on the stabilization. Then we can
have endless discussions on performance.
The SLUB work is still not complete since the intended final fast path
requires new per cpu operations that get thrown one curvball after
another.
prev parent reply other threads:[~2009-07-10 18:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 16:13 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
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 [this message]
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.1.10.0907101453240.14152@gentwo.org \
--to=cl@linux-foundation.org \
--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=rientjes@google.com \
--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 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®