From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Kirkwood: Add memory barriers to kwgbe_send/recv
Date: Fri, 03 Jul 2009 11:15:29 +0200 [thread overview]
Message-ID: <m2iqiann4e.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4A4B996B.7030803@freescale.com> (Scott Wood's message of "Wed, 01 Jul 2009 12:14:19 -0500")
Hi Stefan & Scott,
> 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?
I fully agree with Scott here. Experience has shown that robustness
pays off much more than premature optimizations. If you happen to have
performance problems, then I also seriously advise not to optimize
without actual performance data collected by a profiling run.
This will not be easy for U-Boot but still I've seen so many examples of
effort put into "optimizations" which in the end turned out not to be
relevant for the total performance at all.
Cheers
Detlev
--
Programming X-Windows is like trying to find the square root of pi
using roman numerals.
-- The UNIX Haters Handbook
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2009-07-03 9:15 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
2009-07-03 9:15 ` Detlev Zundel [this message]
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=m2iqiann4e.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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