From: Andrew Morton <akpm@linux-foundation•org>
To: Nick Piggin <nickpiggin@yahoo•com.au>
Cc: netdev@vger•kernel.org, sfr@canb•auug.org.au, matthew@wil•cx,
matthew.r.wilcox@intel•com, chinang.ma@intel•com,
linux-kernel@vger•kernel.org, sharad.c.tripathi@intel•com,
arjan@linux•intel.com, andi.kleen@intel•com,
suresh.b.siddha@intel•com, harita.chilukuri@intel•com,
douglas.w.styner@intel•com, peter.xihong.wang@intel•com,
hubert.nueckel@intel•com, chris.mason@oracle•com,
srostedt@redhat•com, linux-scsi@vger•kernel.org,
andrew.vasquez@qlogic•com, anirban.chakraborty@qlogic•com
Subject: Re: Mainline kernel OLTP performance update
Date: Thu, 15 Jan 2009 23:00:43 -0800 [thread overview]
Message-ID: <20090115230043.57caae5d.akpm@linux-foundation.org> (raw)
In-Reply-To: <200901161746.25205.nickpiggin@yahoo.com.au>
On Fri, 16 Jan 2009 17:46:23 +1100 Nick Piggin <nickpiggin@yahoo•com.au> wrote:
> On Friday 16 January 2009 15:12:10 Andrew Morton wrote:
> > On Fri, 16 Jan 2009 15:03:12 +1100 Nick Piggin <nickpiggin@yahoo•com.au>
> wrote:
> > > I would like to see SLQB merged in mainline, made default, and wait for
> > > some number releases. Then we take what we know, and try to make an
> > > informed decision about the best one to take. I guess that is problematic
> > > in that the rest of the kernel is moving underneath us. Do you have
> > > another idea?
> >
> > Nope. If it doesn't work out, we can remove it again I guess.
>
> OK, I have these numbers to show I'm not completely off my rocker to suggest
> we merge SLQB :) Given these results, how about I ask to merge SLQB as default
> in linux-next, then if nothing catastrophic happens, merge it upstream in the
> next merge window, then a couple of releases after that, given some time to
> test and tweak SLQB, then we plan to bite the bullet and emerge with just one
> main slab allocator (plus SLOB).
That's a plan.
> SLQB tends to be the winner here.
Can you think of anything with which it will be the loser?
next prev parent reply other threads:[~2009-01-16 7:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BC02C49EEB98354DBA7F5DD76F2A9E800317003CB0@azsmsx501.amr.corp.intel.com>
[not found] ` <200901161503.13730.nickpiggin@yahoo.com.au>
[not found] ` <20090115201210.ca1a9542.akpm@linux-foundation.org>
2009-01-16 6:46 ` Mainline kernel OLTP performance update Nick Piggin
2009-01-16 6:55 ` Matthew Wilcox
2009-01-16 7:06 ` Nick Piggin
2009-01-16 7:53 ` Zhang, Yanmin
2009-01-16 10:20 ` Andi Kleen
2009-01-20 5:16 ` Zhang, Yanmin
2009-01-21 23:58 ` Christoph Lameter
2009-01-22 8:36 ` Zhang, Yanmin
2009-01-22 9:15 ` Pekka Enberg
2009-01-22 9:28 ` Zhang, Yanmin
2009-01-22 9:47 ` Pekka Enberg
2009-01-23 3:02 ` Zhang, Yanmin
2009-01-23 6:52 ` Pekka Enberg
2009-01-23 8:06 ` Pekka Enberg
2009-01-23 8:30 ` Zhang, Yanmin
2009-01-23 8:40 ` Pekka Enberg
2009-01-23 9:46 ` Pekka Enberg
2009-01-23 15:22 ` Christoph Lameter
2009-01-23 15:31 ` Pekka Enberg
2009-01-23 15:55 ` Christoph Lameter
2009-01-23 16:01 ` Pekka Enberg
2009-01-24 2:55 ` Zhang, Yanmin
2009-01-24 7:36 ` Pekka Enberg
2009-02-12 5:22 ` Zhang, Yanmin
2009-02-12 5:47 ` Zhang, Yanmin
2009-02-12 15:25 ` Christoph Lameter
2009-02-12 16:07 ` Pekka Enberg
2009-02-12 16:03 ` Pekka Enberg
2009-01-26 17:36 ` Christoph Lameter
2009-02-01 2:52 ` Zhang, Yanmin
2009-01-23 8:33 ` Nick Piggin
2009-01-23 9:02 ` Zhang, Yanmin
2009-01-23 18:40 ` care and feeding of netperf (Re: Mainline kernel OLTP performance update) Rick Jones
2009-01-23 18:51 ` Grant Grundler
2009-01-24 3:03 ` Zhang, Yanmin
2009-01-26 18:26 ` Rick Jones
2009-01-16 7:00 ` Andrew Morton [this message]
2009-01-16 7:25 ` Mainline kernel OLTP performance update Nick Piggin
2009-01-16 8:59 ` Nick Piggin
2009-01-16 18:11 ` Rick Jones
2009-01-19 7:43 ` Nick Piggin
2009-01-19 22:19 ` Rick Jones
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=20090115230043.57caae5d.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=andi.kleen@intel$(echo .)com \
--cc=andrew.vasquez@qlogic$(echo .)com \
--cc=anirban.chakraborty@qlogic$(echo .)com \
--cc=arjan@linux$(echo .)intel.com \
--cc=chinang.ma@intel$(echo .)com \
--cc=chris.mason@oracle$(echo .)com \
--cc=douglas.w.styner@intel$(echo .)com \
--cc=harita.chilukuri@intel$(echo .)com \
--cc=hubert.nueckel@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=matthew.r.wilcox@intel$(echo .)com \
--cc=matthew@wil$(echo .)cx \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nickpiggin@yahoo$(echo .)com.au \
--cc=peter.xihong.wang@intel$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sharad.c.tripathi@intel$(echo .)com \
--cc=srostedt@redhat$(echo .)com \
--cc=suresh.b.siddha@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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