Re: [rfc][patch 2/3] x86: fix IO write barriers

> 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?

But yes we should probably just remove this special case to make 
maintenance easier.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [rfc][patch 2/3] x86: fix IO write barriers
    • From: Dave Jones <[email protected]>

• References:
  • [rfc][patch 1/3] x86_64: fence nontemproal stores
    • From: Nick Piggin <[email protected]>
  • [rfc][patch 2/3] x86: fix IO write barriers
    • From: Nick Piggin <[email protected]>
  • Re: [rfc][patch 2/3] x86: fix IO write barriers
    • From: Dave Jones <[email protected]>

• Prev by Date: Re: SLUB performance regression vs SLAB
• Next by Date: Re: SLUB performance regression vs SLAB
• Previous by thread: Re: [rfc][patch 2/3] x86: fix IO write barriers
• Next by thread: Re: [rfc][patch 2/3] x86: fix IO write barriers
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]