Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining

On Saturday 25 February 2006 05:20, Bryan O'Sullivan wrote:
> On some platforms, a regular wmb() is not sufficient to guarantee that
> PCI writes have been flushed to the bus if write combining is in effect.

On what platforms?
 
> It does so by way of a new header file, <linux/system.h>.  This header
> can be a site for oft-replicated code from <asm-*/system.h>, but isn't
> just yet.

linux/system.h looks unnatural to me.
 
> We also define a version of wc_wmb() with the required semantics
> on x86_64.

Leaving i386 out in the cold?

-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: [PATCH] Define wc_wmb, a write barrier for PCI write combining
    • From: "Bryan O'Sullivan" <[email protected]>

• References:
  • [PATCH] Define wc_wmb, a write barrier for PCI write combining
    • From: "Bryan O'Sullivan" <[email protected]>

• Prev by Date: Re: [patch] x86_64: don't use early_printk() during memory init
• Next by Date: Re: 2.6.16-rc4-mm2: drivers/rtc/utils.c should become part of a generic implementation
• Previous by thread: [PATCH] Define wc_wmb, a write barrier for PCI write combining
• Next by thread: Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining
• 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]