From: David Howells <dhowells@redhat.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: "David S. Miller" <davem@davemloft.net>,
Anton Blanchard <anton@samba.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] ?mb() -> smp_?mb() conversion
Date: Tue, 22 Mar 2005 14:27:04 +0000 [thread overview]
Message-ID: <30642.1111501624@redhat.com> (raw)
In-Reply-To: <20050322131316.GC21986@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox <matthew@wil.cx> wrote:
> > > If I remember correctly, the ?mb() routines _were_ the original
> > > SMP memory barriers.
> >
> > Would it be worth renaming the mb/rmb/wmb to io_mb/io_rmb/io_wmb? After
> > all, I believe they should only be used to flush I/O memory accesses. This
> > would, I think, make the distinction between memory barriers for I/O and
> > memory barriers for SMP more obvious.
>
> Are you joking or genuinely confused?
Must be the latter.
As far as I know memory barriers are only used for I/O and SMP. I don't see
where else they should be required.
Of course, the tiny bit of documentation in the kernel sources isn't much
help; it doesn't even mention the smp_*mb() functions.
David
next prev parent reply other threads:[~2005-03-22 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 22:59 [PATCH] ?mb() -> smp_?mb() conversion Anton Blanchard
2005-03-21 23:06 ` David S. Miller
2005-03-22 10:43 ` David Howells
2005-03-22 13:13 ` Matthew Wilcox
2005-03-22 14:27 ` David Howells [this message]
2005-03-22 16:03 ` Anton Blanchard
2005-03-22 16:34 ` Matthew Wilcox
2005-03-22 16:48 ` David Howells
2005-03-22 17:13 ` David S. Miller
2005-03-22 17:44 ` James Bottomley
2005-03-22 18:09 ` Jesse Barnes
2005-03-22 18:00 ` David Howells
2005-03-22 21:59 ` Paul Mackerras
2005-03-22 18:15 ` Jesse Barnes
2005-03-22 18:24 ` Jesse Barnes
2005-03-23 6:23 ` Paul Mackerras
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=30642.1111501624@redhat.com \
--to=dhowells@redhat.com \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.