From: Andi Kleen <ak@suse.de>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, paulus@samba.org, benh@kernel.crashing.org,
bcrl@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Define flush_wc, a way to flush write combining store buffers
Date: Wed, 8 Mar 2006 15:40:18 +0100 [thread overview]
Message-ID: <200603081540.19284.ak@suse.de> (raw)
In-Reply-To: <1141855547.27555.16.camel@localhost.localdomain>
On Wednesday 08 March 2006 23:05, Bryan O'Sullivan wrote:
> On Wed, 2006-03-08 at 15:35 +0100, Andi Kleen wrote:
>
> > > How is this different to mmiowb() ?
> >
> > I think he intends it to be a flush instead of an ordering.
> > (something like CLFLUSH for WC areas)
>
> Exactly. mmiowb guarantees ordering, but says nothing about timing.
> This would guarantee ordering, affect WC store buffers if present, and
> try to work in a timely manner.
Well if you need the flush, not the ordering then I'm not convinced
SFENCE will do that for you. My understanding is that it only guarantees
ordering.
But at least in some earlier message you said you just needed ordering.
-Andi
prev parent reply other threads:[~2006-03-08 22:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 21:31 [PATCH] Define flush_wc, a way to flush write combining store buffers Bryan O'Sullivan
2006-03-08 21:38 ` Benjamin Herrenschmidt
2006-03-08 21:37 ` Benjamin LaHaise
2006-03-08 21:43 ` Bryan O'Sullivan
2006-03-08 14:21 ` Andi Kleen
2006-03-08 21:57 ` Bryan O'Sullivan
2006-03-08 14:38 ` Andi Kleen
2006-03-09 1:26 ` Bryan O'Sullivan
2006-03-08 23:40 ` Benjamin Herrenschmidt
2006-03-09 1:48 ` Bryan O'Sullivan
2006-03-08 22:06 ` Alan Cox
2006-03-08 14:35 ` Andi Kleen
2006-03-08 22:05 ` Bryan O'Sullivan
2006-03-08 14:40 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200603081540.19284.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@kvack.org \
--cc=benh@kernel.crashing.org \
--cc=bos@pathscale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox