All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Nick Piggin <npiggin@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [rfc][patch 2/3] x86: fix IO write barriers
Date: Thu, 4 Oct 2007 15:08:37 -0400	[thread overview]
Message-ID: <20071004190837.GD23300@redhat.com> (raw)
In-Reply-To: <200710042058.27640.ak@suse.de>

On Thu, Oct 04, 2007 at 08:58:27PM +0200, Andi Kleen wrote:
 > On Thursday 04 October 2007 20:41:07 Dave Jones wrote:
 > > On Thu, Oct 04, 2007 at 08:21:59PM +0200, Andi Kleen wrote:
 > >  > On Thursday 04 October 2007 20:10:44 Dave Jones wrote:
 > >  > > On Thu, Oct 04, 2007 at 07:53:16PM +0200, Andi Kleen wrote:
 > >  > >  > 
 > >  > >  > > The only vendor that ever implemented OOSTOREs was Centaur, and they
 > >  > >  > > only did in the Winchip generation of the CPUs.  When they dropped it
 > >  > >  > > from the C3, I asked whether they intended to bring it back, and the
 > >  > >  > > answer was "extremely unlikely".
 > >  > >  > >
 > >  > >  > 
 > >  > >  > Do you know if it made a big performance difference?
 > >  > > 
 > >  > > On the winchip, it was a huge win. I can't remember exact numbers,
 > >  > > but pretty much every benchmark I threw at it at the time showed
 > >  > > significant improvement.
 > >  > 
 > >  > Significant as in >10%?
 > > 
 > > "Worth about 10-20% performance" according to the 2.4.18pre9-ac4
 > > release notes: http://www.linuxtoday.com/news_story.php3?ltsn=2002-02-14-015-20-NW-KN
 > 
 > Are there numbers for a newer kernel available too?

no idea, my winchips died about 5 years ago.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-10-04 19:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  5:21 [rfc][patch 1/3] x86_64: fence nontemproal stores Nick Piggin
2007-10-04  5:22 ` [rfc][patch 2/3] x86: fix IO write barriers Nick Piggin
2007-10-04 17:32   ` Dave Jones
2007-10-04 17:53     ` Andi Kleen
2007-10-04 18:10       ` Dave Jones
2007-10-04 18:21         ` Andi Kleen
2007-10-04 18:41           ` Dave Jones
2007-10-04 18:58             ` Andi Kleen
2007-10-04 19:08               ` Dave Jones [this message]
2007-10-04 20:52                 ` Alan Cox
2007-10-04  5:23 ` [rfc][patch 3/3] x86: optimise barriers Nick Piggin
2007-10-12  8:25   ` Jarek Poplawski
2007-10-12  8:42     ` Helge Hafting
2007-10-12  9:12       ` Jarek Poplawski
2007-10-12  9:44         ` Nick Piggin
2007-10-12 10:04           ` Jarek Poplawski
2007-10-12 12:44         ` Helge Hafting
2007-10-12 13:29           ` Jarek Poplawski
2007-10-15 10:17             ` Helge Hafting
2007-10-15 11:53               ` Jarek Poplawski
2007-10-12  8:57     ` Nick Piggin
2007-10-12  9:55       ` Jarek Poplawski
2007-10-12 10:42         ` Nick Piggin
2007-10-12 11:55           ` Jarek Poplawski
2007-10-12 12:10             ` Jarek Poplawski
2007-10-12 15:13     ` Linus Torvalds
2007-10-15  7:44       ` Jarek Poplawski
2007-10-15  8:09         ` Nick Piggin
2007-10-15  9:10           ` Jarek Poplawski
2007-10-15  9:24             ` Jarek Poplawski
2007-10-16  0:50             ` Nick Piggin
2007-10-16  9:00               ` Jarek Poplawski
2007-10-16  9:14                 ` david
2007-10-16 12:49                   ` Jarek Poplawski
2007-10-15 14:38         ` David Schwartz

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=20071004190837.GD23300@redhat.com \
    --to=davej@redhat.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.