From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: paulus@samba.org, clameter@sgi.com, linux-kernel@vger.kernel.org,
ak@suse.com, holt@sgi.com, linux-ia64@vger.kernel.org,
mpm@selenic.com
Subject: Re: [QUICKLIST 0/6] Arch independent quicklists V1
Date: Thu, 15 Mar 2007 00:22:49 -0800 [thread overview]
Message-ID: <20070315002249.9e531578.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070312.193211.30184040.davem@davemloft.net>
> On Mon, 12 Mar 2007 19:32:11 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> From: David Miller <davem@davemloft.net>
> Date: Mon, 12 Mar 2007 19:26:16 -0700 (PDT)
>
> > From: Paul Mackerras <paulus@samba.org>
> > Date: Tue, 13 Mar 2007 11:37:32 +1100
> >
> > > David Miller writes:
> > >
> > > > I ported this to sparc64 as per the patch below, tested on
> > > > UP SunBlade1500 and 24 cpu Niagara T1000.
> > >
> > > Did you see any performance improvement? We used to have quicklists
> > > on ppc, but I remain to be convinced that they actually help.
> >
> > It shaved about 3 or 4 seconds consistently off of my kernel
> > build on Niagara which usually clocks in just over 4 minutes
> > on this 24 thread machine.
>
> I want to quantify this with the fact that all the cache false sharing
> issues are irrelevant in this test because the L2 cache is shared
> between all of the cpu threads on Niagara.
>
> It was fast just because the quicklists were lighter weight than the
> SLAB stuff.
So... what would happen if sparc64 were to use neither quicklists nor
slab? Just grab these pages from the page allocator and clear them?
next prev parent reply other threads:[~2007-03-15 7:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 2:09 [QUICKLIST 0/6] Arch independent quicklists V1 Christoph Lameter
2007-03-11 2:09 ` [QUICKLIST 1/6] Extract quicklist implementation from IA64 Christoph Lameter
2007-03-11 2:09 ` [QUICKLIST 2/6] i386: quicklist support Christoph Lameter
2007-03-11 3:22 ` William Lee Irwin III
2007-03-11 2:09 ` [QUICKLIST 3/6] i386: Use standard list manipulators for pgd_list Christoph Lameter
2007-03-11 2:09 ` [QUICKLIST 4/6] x86_64: Single Quicklist Christoph Lameter
2007-03-11 7:54 ` Andi Kleen
2007-03-11 16:44 ` Christoph Lameter
2007-03-14 19:49 ` Mel Gorman
2007-03-11 2:09 ` [QUICKLIST 5/6] x86_64: Separate quicklist for pgds Christoph Lameter
2007-03-11 2:09 ` [QUICKLIST 6/6] slub: remove special casing for PAGE_SIZE slabs Christoph Lameter
2007-03-11 20:59 ` [QUICKLIST 0/6] Arch independent quicklists V1 David Miller
2007-03-12 11:12 ` Christoph Lameter
2007-03-12 11:23 ` David Miller
2007-03-12 15:52 ` Robin Holt
2007-03-12 22:51 ` David Miller
2007-03-13 0:37 ` Paul Mackerras
2007-03-13 1:38 ` Christoph Lameter
2007-03-13 2:26 ` David Miller
2007-03-13 2:32 ` David Miller
2007-03-15 8:22 ` Andrew Morton [this message]
2007-03-15 7:31 ` David Miller
2007-03-15 8:39 ` Andrew Morton
2007-03-14 0:41 ` William Lee Irwin III
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=20070315002249.9e531578.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.com \
--cc=clameter@sgi.com \
--cc=davem@davemloft.net \
--cc=holt@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paulus@samba.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