Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining
- From: Roland Dreier <rdreier@xxxxxxxxx>
- Date: Tue, 28 Feb 2006 07:42:52 -0800
Jes> Could you explain why the current mmiowb() API won't suffice
Jes> for this? It seems that this is basically trying to achieve
Jes> the same thing.
I don't believe mmiowb() is at all the same thing. mmiowb() is all
about ordering writes between _different_ CPUs without incurring the
cost of flushing posted writes by issuing a read on the bus. wc_wmb()
would just act like a true wmb(), even when using write-combining
regions on x86 -- in other words, there would be no cross-CPU synchronization.
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
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: Jes Sorensen
- Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining
- References:
- [PATCH] Define wc_wmb, a write barrier for PCI write combining
- From: Bryan O'Sullivan
- Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining
- From: Jes Sorensen
- [PATCH] Define wc_wmb, a write barrier for PCI write combining
- Prev by Date: Re: i386 cpu hotplug bug - instant reboot when onlining secondary
- Next by Date: Re: [PATCH] Fixup ahci suspend / resume
- Previous by thread: Re: [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):
Relevant Pages
|
|
