Alan Cox <alan@redhat.com> wrote: > then on some NUMA infrastructures the order may not be as you expect. Oh, yuck! Okay... does NUMA guarantee the same for ordinary memory accesses inside the critical 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/
- Follow-Ups:
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: Andi Kleen <ak@suse.de>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- References:
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: Alan Cox <alan@redhat.com>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: Alan Cox <alan@redhat.com>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: Alan Cox <alan@redhat.com>
- [PATCH] Document Linux's memory barriers
- From: David Howells <dhowells@redhat.com>
- [PATCH] Document Linux's memory barriers [try #2]
- From: David Howells <dhowells@redhat.com>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: David Howells <dhowells@redhat.com>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- From: David Howells <dhowells@redhat.com>
- Re: [PATCH] Document Linux's memory barriers [try #2]
- Prev by Date: Re: Nigel's work and the future of Suspend2.
- Next by Date: RE: [PATCH] ftruncate on huge page couldn't extend hugetlb file
- 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):
 |