Messages in this thread |  | | | From | David Howells <> | | Subject | Re: [PATCH] Document Linux's memory barriers [try #2] | | Date | Wed, 08 Mar 2006 18:35:07 +0000 |
| |
Alan Cox <alan@redhat.com> 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |