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

On Wednesday, March 8, 2006 4:37 pm, Paul Mackerras wrote:
> Matthew Wilcox writes:
> > Looking at the SGI implementation, it's smarter than you think. 
> > Looks like there's a register in the local I/O hub that lets you
> > determine when this write has been queued in the appropriate
> > host->pci bridge.
>
> Given that mmiowb takes no arguments, how does it know which is the
> appropriate PCI host bridge?

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.

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/

---

• Follow-Ups:
  • Re: [PATCH] Document Linux's memory barriers [try #2]
    • From: Paul Mackerras <[email protected]>

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

• Prev by Date: [PATCH] dcdbas: dcdbas_pdev referenced after platform_device_unregister on exit
• 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]