From: Octave <oles@ovh.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: NAPI 8139too.c for 2.4.23
Date: Tue, 2 Dec 2003 00:00:13 +0100 [thread overview]
Message-ID: <20031201230013.GM4313@ovh.net> (raw)
In-Reply-To: <20031201205533.GA15846@gtf.org>
> Is there any chance you could do some benchmark runs with ttcp or
> somesuch?
I tested on 6-7 servers running with
eepro eth0: Intel Corp. 82557/8/9 [Ethernet Pro 100], 00:E0:18:01:78:6C, IRQ 10.
realtek 8139too with NAPI 8139too Fast Ethernet driver 0.9.27
realtek 8139too with no NAPI (standard driver with soft polling)
If this quick test is correct, realtek 8139too's driver works as good as
eepro's driver.
Octave
>> from realtek (no NAPI) to realtek (no NAPI)
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from
ttcp-r: 327680000 bytes in 42.90 real seconds = 59671.99 Kbit/sec +++
ttcp-r: 224852 I/O calls, msec/call = 0.20, calls/sec = 5241.16
ttcp-r: 0.1user 1.5sys 0:42real 3% 0i+0d 0maxrss 0+2pf 0+0csw
>> from eepro to eepro
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from
ttcp-r: 327680000 bytes in 28.33 real seconds = 90379.31 Kbit/sec +++
ttcp-r: 225058 I/O calls, msec/call = 0.13, calls/sec = 7945.54
ttcp-r: 0.2user 4.2sys 0:28real 15% 0i+0d 0maxrss 0+2pf 0+0csw
>> from realtek (NAPI) to realtek (NAPI)
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from
ttcp-r: 327680000 bytes in 29.21 real seconds = 87644.11 Kbit/sec +++
ttcp-r: 225735 I/O calls, msec/call = 0.13, calls/sec = 7728.26
ttcp-r: 0.0user 1.7sys 0:29real 6% 0i+0d 0maxrss 0+2pf 0+0csw
>> from eepro to realtek (no NAPI)
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from
ttcp-t: 327680000 bytes in 34.32 real seconds = 74594.99 Kbit/sec +++
ttcp-t: 40000 I/O calls, msec/call = 0.88, calls/sec = 1165.55
ttcp-t: 0.0user 1.2sys 0:34real 3% 0i+0d 0maxrss 0+2pf 0+0csw
>> from realtek (NAPI) to realtek (no NAPI)
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from
ttcp-r: 327680000 bytes in 32.60 real seconds = 78532.74 Kbit/sec +++
ttcp-r: 225544 I/O calls, msec/call = 0.15, calls/sec = 6918.98
ttcp-r: 0.1user 1.6sys 0:32real 5% 0i+0d 0maxrss 0+2pf 0+0csw
>> from realtek (NAPI) to eepro
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from
ttcp-r: 327680000 bytes in 34.02 real seconds = 75250.05 Kbit/sec +++
ttcp-r: 225685 I/O calls, msec/call = 0.15, calls/sec = 6633.91
ttcp-r: 0.1user 3.7sys 0:34real 11% 0i+0d 0maxrss 0+2pf 0+0csw
next prev parent reply other threads:[~2003-12-01 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 20:50 NAPI 8139too.c for 2.4.23 Octave
2003-12-01 20:55 ` Jeff Garzik
2003-12-01 23:00 ` Octave [this message]
2003-12-01 23:39 ` Ben Greear
2003-12-02 3:47 ` Jeff Garzik
2003-12-01 21:13 ` Marcello
2003-12-01 22:32 ` Marcello
2003-12-01 22:54 ` Marcello
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=20031201230013.GM4313@ovh.net \
--to=oles@ovh.net \
--cc=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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 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.