From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: Change the mandatory barriers implementation
Date: Mon, 1 Mar 2010 03:44:28 +0000 [thread overview]
Message-ID: <20100301034428.GF8391@shareable.org> (raw)
In-Reply-To: <1267199030.14703.28.camel@e102109-lin.cambridge.arm.com>
Catalin Marinas wrote:
> A better implementation would be this:
>
> #ifndef CONFIG_SMP
> #define smp_mb() barrier()
> #define smp_rmb() barrier()
> #define smp_wmb() barrier()
> #else
> #define smp_mb() dsb()
> #define smp_rmb() mb()
> #define smp_wmb() dsb()
> #endif
>
> Since the mb() may have other effects like draining the L2 write buffer
> which is definitely not needed for the SMP barriers.
>
> Anyway, the above change to smp_*mb() would probably have a performance
> impact especially with spinlocks.
>
> I can see that the driver situation you described appears in other
> drivers as well. Whether this is a correct usage model I can't tell. It
> may be worth going with this on linux-arch. PowerPC for example uses a
> light barrier for the smp_wmb() case which doesn't ensure ordering
> between accesses to normal vs I/O memory.
I agree, it looks like some confusion about the meaning of smp_wmb()
for ordering w.r.t. I/O, DMA and interrupts has crept in.
It would be good to clarify it.
-- Jamie
next prev parent reply other threads:[~2010-03-01 3:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 11:01 [PATCH 1/4] ARM: Change the mandatory barriers implementation Catalin Marinas
2010-02-23 11:10 ` Russell King - ARM Linux
2010-02-23 12:16 ` Catalin Marinas
2010-02-23 12:30 ` Russell King - ARM Linux
2010-02-23 15:12 ` Catalin Marinas
2010-02-23 15:24 ` Russell King - ARM Linux
2010-02-23 16:02 ` Catalin Marinas
2010-02-23 18:03 ` Russell King - ARM Linux
2010-02-23 18:07 ` Catalin Marinas
2010-03-01 3:37 ` Jamie Lokier
2010-02-26 15:43 ` Catalin Marinas
2010-03-01 3:44 ` Jamie Lokier [this message]
2010-02-23 12:21 ` Catalin Marinas
2010-02-23 12:31 ` Russell King - ARM Linux
2010-02-23 11:35 ` Shilimkar, Santosh
2010-02-23 11:41 ` Russell King - ARM Linux
2010-02-23 17:33 ` Russell King - ARM Linux
2010-02-23 17:58 ` Catalin Marinas
2010-02-23 18:04 ` Catalin Marinas
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=20100301034428.GF8391@shareable.org \
--to=jamie@shareable.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).