Alan Cox <[email protected]> wrote: > spin_unlock ensures that local CPU writes before the lock are visible > to all processors before the lock is dropped but it has no effect on > I/O ordering. Just a need for clarity. So I can't use spinlocks in my driver to make sure two different CPUs don't interfere with each other when trying to communicate with a device because the spinlocks don't guarantee that I/O operations will stay in effect within the locking section? David - 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] Document Linux's memory barriers [try #2]
- From: David Howells <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: David Howells <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: Alan Cox <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- References:
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: Alan Cox <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: Alan Cox <[email protected]>
- [PATCH] Document Linux's memory barriers
- From: David Howells <[email protected]>
- [PATCH] Document Linux's memory barriers [try #2]
- From: David Howells <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: David Howells <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- Prev by Date: Re: [linux-usb-devel] Re: Fw: Re: oops in choose_configuration()
- Next by Date: RE: SATA ATAPI AHCI error messages?
- Previous by thread: Re: [PATCH] Document Linux's memory barriers [try #2]
- Next by thread: Re: [PATCH] Document Linux's memory barriers [try #2]
- Index(es):
 |