From: Roland Dreier <rdreier@cisco.com>
To: Jes Sorensen <jes@sgi.com>
Cc: "Bryan O'Sullivan" <bos@pathscale.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: Why is wmb() a no-op on x86_64?
Date: Wed, 18 Jan 2006 12:07:23 -0800 [thread overview]
Message-ID: <ada4q41wb9g.fsf@cisco.com> (raw)
In-Reply-To: <yq04q41qxcw.fsf@jaguar.mkp.net> (Jes Sorensen's message of "18 Jan 2006 12:06:39 -0500")
Bryan> On x86_64, we fiddle with the MTRRs to enable write
Bryan> combining, which makes a huge difference to performance.
Bryan> It's not clear to me what we should even do on other
Bryan> architectures, since the only generic entry point that even
Bryan> exposes write combining is pci_mmap_page_range, which is
Bryan> for PCI mmap through userspace, and half the arches I've
Bryan> looked at ignore its write_combine parameter.
Jes> A job for mmiowb() perhaps?
I don't think the semantics of mmiowb() do what is desired here.
mmiowb() is all about ordering writes between separate CPUs, and the
issue at hand here is that write-combining buffers might reorder
writes from a single CPU.
- R.
prev parent reply other threads:[~2006-01-18 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 16:23 Why is wmb() a no-op on x86_64? Bryan O'Sullivan
2006-01-18 16:29 ` Andi Kleen
2006-01-18 16:52 ` Bryan O'Sullivan
2006-01-18 17:06 ` Jes Sorensen
2006-01-18 17:23 ` Bryan O'Sullivan
2006-01-18 17:31 ` [discuss] " Andi Kleen
2006-01-19 10:03 ` Jes Sorensen
2006-01-18 20:07 ` Roland Dreier [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=ada4q41wb9g.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ak@suse.de \
--cc=bos@pathscale.com \
--cc=discuss@x86-64.org \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.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