| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 4 Oct 2007 14:10:44 -0400 From: Dave Jones <davej@...hat.com> To: Andi Kleen <ak@...e.de> Cc: Nick Piggin <npiggin@...e.de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [rfc][patch 2/3] x86: fix IO write barriers 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. > But yes we should probably just remove this special case to make > maintenance easier. It's CONFIG_SMP anyway, which none of the winchips were. SMP+OOSTORE just didn't happen, and I'd be surprised if any vendor makes it happen any time soon. (Even if so, it's likely we'd need to make additional changes anyway, so adding it back shouldn't be a big deal.) Dave -- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists