Re: [PATCH] Define flush_wc, a way to flush write combining store buffers

On Mer, 2006-03-08 at 13:31 -0800, Bryan O'Sullivan wrote:
> flush_wc() says nothing about whether {A,B,C} may be reordered with
> respect to each other, or whether {D,E} may, but it guarantees that
> {A,B,C} will make it off-CPU before {D,E}.  An arch that implements
> flush_wc() should make the stores occur immediately, if possible.

How is this different to mmiowb() ?


-
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] Define flush_wc, a way to flush write combining store buffers
  - From: Andi Kleen <[email protected]>

References:
- [PATCH] Define flush_wc, a way to flush write combining store buffers
  - From: "Bryan O'Sullivan" <[email protected]>

Prev by Date: Re: [PATCH] Document Linux's memory barriers
Next by Date: Re: [PATCH] Define flush_wc, a way to flush write combining store buffers
Previous by thread: Re: [PATCH] Define flush_wc, a way to flush write combining store buffers
Next by thread: Re: [PATCH] Define flush_wc, a way to flush write combining store buffers
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]