From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] pio barriers
Date: Mon, 10 Dec 2001 22:47:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805669@msgid-missing> (raw)
I noticed that in asm-ia64/system.h there's a comment that reads:
/*
...
* Note: "mb()" and its variants cannot be used as a fence to order
* accesses to memory mapped I/O registers. For that, mf.a needs to
* be used. However, we don't want to always use mf.a because (a)
* it's (presumably) much slower than mf and (b) mf.a is supported for
* sequential memory pages only.
*/
Is there a macro (e.g. piob() or mmiob()) to wrap mf.a or are users
expected to call it explicitly when they need it? If there is no
macro, I'd like to add one, as I think it will be necessary to
properly support our NUMA platform.
Thanks,
Jesse
next reply other threads:[~2001-12-10 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 22:47 Jesse Barnes [this message]
2001-12-10 22:57 ` [Linux-ia64] pio barriers Jack Steiner
2001-12-10 23:00 ` Jesse Barnes
2001-12-10 23:58 ` David Mosberger
2001-12-11 0:23 ` Jesse Barnes
2001-12-11 0:44 ` David Mosberger
2001-12-11 0:55 ` Jesse Barnes
2001-12-11 5:30 ` David Mosberger
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=marc-linux-ia64-105590698805669@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@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