ck ensures that the IO device sees stores from a single CPU
at a time. wmb() ensures that CPU A and CPU B see the effect
of cacheable stores in the same order as eachother. mmiowb()
ensures that the IO device has seen all the uncacheable stores from
CPU A before CPU B sees the cacheable stores fro
On Wed, 29 Aug 2007, Nick Piggin wrote:
> On Tue, Aug 28, 2007 at 03:56:28PM -0500, Brent Casavant wrote:
> > The simplistic method to solve this is a lock around the section
> > issuing IOs, thereby ensuring serialization of access to the IO
> > device. However, as SN
ing on the user-level
driver effort including a capability similar to mmiowb()? If we
had that capability we could eventually do away with the change
mentioned above. But that would come after all user-level drivers
were coded to include the mmiowb()-like calls, and existing drivers
which provide mma
without fear of the unlock's memory write passing
any outstanding IOs from that CPU.
Brent
--
Brent Casavant All music is folk music. I ain't
[EMAIL PROTECTED]never heard a horse sing a song.
Silicon Graphics, Inc.-- Louis Ar
