Re: [PATCH] Document Linux's memory barriers [try #2]

On Wednesday, March 08, 2006 5:36 pm, Paul Mackerras wrote:
> Jesse Barnes writes:
> > It uses a per-node address space to reference the local bridge. 
> > The local bridge then waits until the remote bridge has acked the
> > write before, then sets the outstanding write register to the
> > appropriate value.
>
> That sounds like mmiowb can only be used when preemption is disabled,
> such as inside a spin-locked region - is that right?

There's a scheduler hook to flush things if a process moves.  I think 
Brent Casavant submitted that patch recently.

Jesse
-
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/

---

• 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: Jesse Barnes <[email protected]>
  • Re: [PATCH] Document Linux's memory barriers [try #2]
    • From: Paul Mackerras <[email protected]>

• Prev by Date: Re: [PATCH] mm: yield during swap prefetching
• Next by Date: Re: [PATCH] Document Linux's memory barriers [try #2]
• 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):
  • 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]