From: "David S. Miller" <davem@caip.rutgers.edu>
To: torvalds@cs.helsinki.fi
Cc: lmlinux@neteng.engr.sgi.com, adrian@remus.rutgers.edu
Subject: ccpenguin
Date: Mon, 18 Mar 1996 09:08:02 -0500 [thread overview]
Message-ID: <199603181408.JAA03959@huahaga.rutgers.edu> (raw)
Not too bad at all. Pretty spiffy machine I guess. Although no match
for Linus's ev5 running Linux. But when I get the port done on this
thing I'll have comparable numbers ;-)
Remember, no forwarding of this stuff.
L M B E N C H 1 . 0 S U M M A R Y
------------------------------------
Processor, Processes - times in microseconds
--------------------------------------------
Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc
Syscall Process Process Process lat ctxsw ctxsw
--------- ------------- ---- ------- ------- ------- ------- ---- ------ ------
ccpenguin SunOS 5.5.1 167 5 3.4K 19.5K 37K 184 13 19
*Local* Communication latencies in microseconds
-----------------------------------------------
Host OS Pipe UDP RPC/ TCP RPC/
UDP TCP
--------- ------------- ------- ------- ------- ------- -------
ccpenguin SunOS 5.5.1 54 197 273 163 330
*Local* Communication bandwidths in megabytes/second
----------------------------------------------------
Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem
reread reread (libc) (hand) read write
--------- ------------- ---- ---- ------ ------ ------ ------ ---- -----
ccpenguin SunOS 5.5.1 61 50.8 138.6 96.1 171 66 115 156
Memory latencies in nanoseconds
(WARNING - may not be correct, check graphs)
--------------------------------------------
Host OS Mhz L1 $ L2 $ Main mem TLB Guesses
--------- ------------- --- ---- ---- -------- --- -------
ccpenguin SunOS 5.5.1 167 6 41 265 492
reply other threads:[~1996-03-18 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199603181408.JAA03959@huahaga.rutgers.edu \
--to=davem@caip.rutgers.edu \
--cc=adrian@remus.rutgers.edu \
--cc=lmlinux@neteng.engr.sgi.com \
--cc=torvalds@cs.helsinki.fi \
/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.