From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Kirkwood: Add memory barriers to kwgbe_send/recv
Date: Wed, 01 Jul 2009 12:14:19 -0500 [thread overview]
Message-ID: <4A4B996B.7030803@freescale.com> (raw)
In-Reply-To: <200907011909.21754.sr@denx.de>
Stefan Roese wrote:
> I know that we advertised the usage of the io accessor functions for quite
> some time now. But I'm not so sure here anymore. One disadvantage of this
> usage could be speed penalty by the usage of too many unnecessary barriers
> (included via the accessor functions on some platforms).
Hot paths (or tiny bootstraps) can be optimized if needed, but why
invite screwups for the majority of code?
-Scott
next prev parent reply other threads:[~2009-07-01 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 15:16 [U-Boot] [PATCH] arm: Kirkwood: Add memory barriers to kwgbe_send/recv Simon Kagstrom
2009-07-01 16:56 ` Detlev Zundel
2009-07-01 17:09 ` Stefan Roese
2009-07-01 17:14 ` Scott Wood [this message]
2009-07-03 9:15 ` Detlev Zundel
2009-07-01 16:57 ` Prafulla Wadaskar
2009-07-02 6:47 ` Simon Kagstrom
2009-07-02 8:12 ` Prafulla Wadaskar
2009-07-03 8:57 ` Detlev Zundel
2009-07-04 23:52 ` Wolfgang Denk
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=4A4B996B.7030803@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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