Hello,
I've just used ttcp.
On the client side, I did cat/pipe a DVD iso file into ttcp.
The server (gem0, enabled=3c00) says:
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from 10.15.5.53
ttcp-r: 7782250496 bytes in 695.00 real seconds = 10935.00 KB/sec +++
ttcp-r: 3618027 I/O calls, msec/call = 0.20, calls/sec = 5205.78
ttcp-r: 1.2user 60.0sys 11:35real 8% 0i+0d 0maxrss 0+2pf 3617047+854csw
The client (rtk0) says:
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ->
guarana
ttcp-t: socket
ttcp-t: connect
ttcp-t: 7782250496 bytes in 694.49 real seconds = 10943.05 KB/sec +++
ttcp-t: 949982 I/O calls, msec/call = 0.75, calls/sec = 1367.88
ttcp-t: 2.0user 167.5sys 11:34real 24% 0i+0d 0maxrss 0+3799927pf 0+0csw
This looks like a "decent" 100MBits traffic rate :-)
Regards,
Jo
On Fri, Mar 14 2008 - 01:53, Izumi Tsutsui wrote:
> (I don't subscribe this list so please Cc: me)
>
> Well, I'm not sure if it's a problem on the driver or chip,
> but as you can see in a comment in src/sys/dev/ic/rtl81x9.c
> http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/dev/ic/rtl81x9.c?rev=1.81
> the Realtek 8139 is not so smart.
> On the other hand, modern CPU is so overmuscled
> to handle interrupt storm from such dumb device.
>
> Anyway, ~10000 intrs/sec is not surpising for me
> because find(1) may send/receive a bunch of small packets.
>
> but re(4) (RTL8169) and ex(4) (3C905B) on the same machine
> also show the similar numbers.
>
> I'd suggest to use proper benchmark programs (like ttcp or netperf)
> to measure performance. A number of interrupts is not so important
> if (overmuscled) CPU is still idle, but bandwidth on the bus-master
> device may limit network throughput.
> ---
> Izumi Tsutsui
Attachment:
pgprQd_sWrdKn.pgp
Description: PGP signature