From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: akpm@osdl.org, ak@suse.de, paulus@samba.org, bcrl@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Define flush_wc, a way to flush write combining store buffers
Date: Thu, 09 Mar 2006 08:38:39 +1100 [thread overview]
Message-ID: <1141853919.11221.183.camel@localhost.localdomain> (raw)
In-Reply-To: <e27c8e0061e03594b3e1.1141853501@localhost.localdomain>
On Wed, 2006-03-08 at 13:31 -0800, Bryan O'Sullivan wrote:
> In some circumstances, a CPU may perform stores to memory in non-program
> order, or held in on-chip store buffers for a potentially long time.
> These kinds of circumstances include:
>
> - Stores to a PCI MMIO region that has write combining enabled
>
> - Use of non-temporal store instructions
>
> - The CPU's memory model permitting weak store ordering
>
> This patch introduces a new macro, flush_wc(), that flushes any pending
> stores from the local CPU's write combining store buffers, if the CPU has
> such a capability. If the CPU doesn't provide explicit control over write
> combining, flush_wc() is simply an alias for wmb(). Here is an example:
I think people already don't undersatnd the existing gazillion of
barriers we have with quite unclear semantics in some cases, it's not
time to add a new one ...
Ben.
next prev parent reply other threads:[~2006-03-08 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 21:31 Bryan O'Sullivan
2006-03-08 21:38 ` Benjamin Herrenschmidt [this message]
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
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=1141853919.11221.183.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bcrl@kvack.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
Powered by JetHome