From: Rob Latham <rob@terizla.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: glibc: optimized ppc bcopy
Date: Fri, 11 Apr 2003 16:04:49 -0500 [thread overview]
Message-ID: <20030411210449.GC92837@terizla.org> (raw)
i noticed something when comparing lmbench numbers between os x and
linux on the same hardware: linux beats os x at every category except
one: Bcopy (libc)
*Local* Communication bandwidths in MB/s - bigger is better
-----------------------------------------------------------
Host OS Pipe AF TCP File Mmap Bcopy Bcopy Mem Mem
UNIX reread reread (libc) (hand) read write
--------- ------------- ---- ---- ---- ------ ------ ------ ------ ---- -----
aragorn Linux 2.4.20- 198. 216. 90.1 206.5 173.1 122.8 124.2 173. 358.3
os-x Darwin 6.4 124. 121. 80.5 150.6 178.1 239.8 123.4 178. 411.9
So i looked a bit closer at glibc: there are no optimized powerpc
string or memory operations. ( later confirmed by the glibc web
pages)
I know there are a zillion powerpc variants: would it be hard to
write assembly that works with all of them? I know almost zero about
powerpc assembly, but this might be a fun place to start learning. Of
course, if anyone else has already started such an undertaking, i'll
defer to them and go work on something else.
For those curious, the full lmbench run can be found here:
http://terizla.org/~robl/pbook/benchmarks/lmbench-linux_vs_osx.1
(linux does quite well :> )
==rob
--
Rob Latham Chicago, IL USA
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-04-11 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 21:04 Rob Latham [this message]
2003-04-11 21:37 ` glibc: optimized ppc bcopy Kenneth Johansson
2003-04-11 22:21 ` Rob Baxter
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=20030411210449.GC92837@terizla.org \
--to=rob@terizla.org \
--cc=linuxppc-dev@lists.linuxppc.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).