From: Christoph Lameter <clameter@sgi.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: SLUB: Increasing partial pages
Date: Wed, 16 Jan 2008 14:28:44 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0801161421240.12024@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080116221618.GB11559@parisc-linux.org>
On Wed, 16 Jan 2008, Matthew Wilcox wrote:
> About 0.1-0.2% 0.3% is considered significant.
The results are that stable? A kernel compilation which slightly
rearranges cachelines due to code and data changes typically leads to a
larger variance on my 8 way box (gets even larger under NUMA). I would
expect that the variations on a database load would be more significant.
I repeatedly saw patches from Intel to do minor changes to SLAB that
increase performance by 0.5% or so (like the recent removal of a BUG_ON
for performance reasons). These do not regress again when you build a
newer kernel release?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-01-16 22:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 19:59 SLUB: Increasing partial pages Matthew Wilcox
2008-01-16 20:39 ` Christoph Lameter
2008-01-16 21:41 ` Matthew Wilcox
2008-01-16 22:01 ` Christoph Lameter
2008-01-16 22:16 ` Matthew Wilcox
2008-01-16 22:28 ` Christoph Lameter [this message]
2008-01-18 19:14 ` Matthew Wilcox
2008-01-22 20:00 ` Christoph Lameter
2008-01-22 22:35 ` Matthew Wilcox
2008-01-22 23:00 ` Christoph Lameter
2008-02-16 19:07 ` Matthew Wilcox
2008-02-16 19:34 ` Christoph Lameter
2008-05-05 18:04 ` Pekka Enberg
2008-01-18 19:54 ` Matthew Wilcox
2008-01-22 19:42 ` 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=Pine.LNX.4.64.0801161421240.12024@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
/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;
as well as URLs for NNTP newsgroup(s).