public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Matt Mackall <mpm@selenic.com>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH][2.6] Completely out of line spinlocks / i386
Date: Wed, 11 Aug 2004 23:59:15 +0200	[thread overview]
Message-ID: <20040811215915.GA21812@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0408072123590.19619@montezuma.fsmlabs.com>

Hi!

> Pulled from the -tiny tree, the focus of this patch is for reduced kernel
> image size but in the process we benefit from improved cache performance
> since it's possible for the common text to be present in cache. This is
> probably more of a win on shared cache multiprocessor systems like
> P4/Xeon HT. It's been benchmarked with bonnie++ on 2x and 4x PIII (my
> ideal target would be a 4x+ logical cpu Xeon).
> 
> The bonnie++ results are here, the hostnames are of the form stpN-000 with
> N denoting how many processors in the system. In a nutshell there doesn't
> appear to be any performance regressions.

Fine, so perhaps we do not want config option?
									Pavel

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  parent reply	other threads:[~2004-08-11 22:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-08  4:49 [PATCH][2.6] Completely out of line spinlocks / i386 Zwane Mwaikambo
2004-08-08  5:01 ` Linus Torvalds
2004-08-08  5:17   ` Zwane Mwaikambo
2004-08-08  5:21     ` Linus Torvalds
2004-08-08  6:00       ` Zwane Mwaikambo
2004-08-08 12:33         ` Andreas Schwab
2004-08-08 18:26           ` Zwane Mwaikambo
2004-08-11 21:59 ` Pavel Machek [this message]
2004-08-11 22:13   ` Linus Torvalds
2004-08-11 22:23     ` William Lee Irwin III
2004-08-12  0:01     ` Keith Owens
2004-08-12  0:39       ` David S. Miller
2004-08-12  0:54       ` Zwane Mwaikambo
2004-08-12  1:01       ` William Lee Irwin III
2004-08-12  1:37         ` Zwane Mwaikambo
2004-08-12  2:04           ` William Lee Irwin III
2004-08-12  7:20             ` William Lee Irwin III
2004-08-12  7:23               ` William Lee Irwin III
2004-08-12  7:25                 ` William Lee Irwin III
2004-08-12  8:12               ` Zwane Mwaikambo
2004-08-12  8:11                 ` William Lee Irwin III
2004-08-12  8:54                   ` William Lee Irwin III
2004-08-13  8:01               ` William Lee Irwin III
2004-08-13  9:16                 ` William Lee Irwin III
2004-08-13  9:30                   ` William Lee Irwin III
2004-08-13  9:46                     ` William Lee Irwin III
2004-08-13 10:05                       ` William Lee Irwin III
2004-08-13 10:23                         ` William Lee Irwin III
2004-08-13 10:39                           ` William Lee Irwin III
2004-08-13 14:15                             ` Zwane Mwaikambo
2004-08-13 14:29                               ` 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=20040811215915.GA21812@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=torvalds@osdl.org \
    --cc=zwane@linuxpower.ca \
    /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