From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: willy@linux.intel.com, Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [git pull] SLUB updates for 2.6.25
Date: Mon, 4 Feb 2008 17:15:05 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0802041700170.5438@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200802051142.20413.nickpiggin@yahoo.com.au>
On Tue, 5 Feb 2008, Nick Piggin wrote:
> Anyway, not saying the operations are useless, but they should be
> made available to core kernel and implemented per-arch. (if they are
> found to be useful)
The problem is to establish the usefulness. These measures may bring 1-2%
in a pretty unstable operation mode assuming that the system is doing
repetitive work. The micro optimizations seem to be often drowned out
by small other changes to the system.
There is the danger that a gain is seen that is not due to the patch but
due to other changes coming about because code is moved since patches
change execution paths.
Plus they may be only possible on a specific architecture. I know that our
IA64 hardware has special measures ensuring certain behavior of atomic ops
etc, I guess Intel has similar tricks up their sleeve. At 8p there are
likely increasing problems with lock starvation where your ticketlock
helps. That is why I thought we better defer the stuff until there is some
more evidence that these are useful.
I got particularly nervous about these changes after I saw small
performance drops due to the __unlock patch on the dual quad. That should
have been a consistent gain.
--
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>
prev parent reply other threads:[~2008-02-05 1:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 20:08 [git pull] SLUB updates for 2.6.25 Christoph Lameter
2008-02-04 22:28 ` Andrew Morton
2008-02-04 22:30 ` Andrew Morton
2008-02-04 23:04 ` Christoph Lameter
2008-02-04 23:10 ` Nick Piggin
2008-02-04 23:47 ` Christoph Lameter
2008-02-05 0:05 ` Nick Piggin
2008-02-05 0:22 ` Christoph Lameter
2008-02-05 0:32 ` Christoph Lameter
2008-02-05 0:42 ` Nick Piggin
2008-02-05 1:15 ` 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=Pine.LNX.4.64.0802041700170.5438@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=torvalds@linux-foundation.org \
--cc=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).