Re: [patch 2] mm: speculative get_page

From: Nick Piggin <[email protected]>
Subject: Re: [patch 2] mm: speculative get_page
Date: Tue, 28 Jun 2005 14:50:31 +1000

> William Lee Irwin III wrote:
> 
> >On Tue, Jun 28, 2005 at 11:42:16AM +1000, Nick Piggin wrote:
> >
> >spin_unlock() does not imply a memory barrier.
> >
> 
> Intriguing...

BTW, I disagree with this assertion.  spin_unlock() does imply a
memory barrier.

All memory operations before the release of the lock must execute
before the lock release memory operation is globally visible.
-
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 2] mm: speculative get_page
    • From: Jesse Barnes <[email protected]>
  • Re: [patch 2] mm: speculative get_page
    • From: William Lee Irwin III <[email protected]>
  • Re: [patch 2] mm: speculative get_page
    • From: Nick Piggin <[email protected]>

• References:
  • Re: [patch 2] mm: speculative get_page
    • From: Nick Piggin <[email protected]>
  • Re: [patch 2] mm: speculative get_page
    • From: William Lee Irwin III <[email protected]>
  • Re: [patch 2] mm: speculative get_page
    • From: Nick Piggin <[email protected]>

• Prev by Date: pcmcia: release_class patch concern
• Next by Date: [PATCH]MTRR suspend/resume cleanup
• Previous by thread: Re: [patch 2] mm: speculative get_page
• Next by thread: Re: [patch 2] mm: speculative get_page
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]