* Performance of bonding driver with e1000
@ 2009-11-23 18:06 J.A. Magallón
0 siblings, 0 replies; only message in thread
From: J.A. Magallón @ 2009-11-23 18:06 UTC (permalink / raw)
To: NetDev
Hi...
I have two boxes which I linked together via 2x gigabit interfaces and a
3Com switch. Each interface is:
02:0a.0 Ethernet controller: Intel Corporation 82541EI Gigabit Ethernet Controller
02:0b.0 Ethernet controller: Intel Corporation 82541EI Gigabit Ethernet Controller
I use the e1000 driver.
The switch is private for them, so there is no more taffic.
Boxes are P4-HT@2.8, 3Gb of RAM.
Both interfaces alone work pretty well (performance measured with iperf):
[ 5] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 41252
[ ID] Interval Transfer Bandwidth
[ 5] 0.0-10.0 sec 1.00 GBytes 860 Mbits/sec
[ 4] local 192.168.2.2 port 5001 connected with 192.168.2.1 port 39275
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.0 sec 1024 MBytes 858 Mbits/sec
I loaded bonding driver with no parameters, and using iperf I get:
[ 4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 41254
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.0 sec 741 MBytes 621 Mbits/sec
In the node which receives, two instances of iftop on slave interfaces
show that load is balanced, but none flies higher than about 300 Mb/s.
Any ideas ?
If you guess something and need more info, I will provide it.
TIA
--
J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
\ It's better when it's free
Mandriva Linux release 2010.0 (Cooker) for x86_64
Linux 2.6.29.3-desktop-1mnb (gcc 4.3.2 (GCC) #1 Wed May
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-11-23 18:11 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-23 18:06 Performance of bonding driver with e1000 J.A. Magallón
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).