Support Team <[email protected]> wrote:
>Yes, same VLAN setup in the software does not work for 82546 chip. The
>setup in software are identical,
>other than 82546 load E1000 driver and 82573 load E1000E driver, nothing
>else changed in software or
>test environment. If we can see 82546/MT adapter can get 2GB/s in bond
>mode, we will be happy.
Some bonding things to check:
ip route show
Make sure no interfaces (the slaves) have routes that supercede
the route for the bond itself.
cat /proc/net/bonding/bond0 [or whatever bond device you have]
Make sure the options you think you have match what bonding is
seeing (particularly the xmit_hash_policy if your throughput test is
many connections but not many discrete peers).
Also in the proc file, make sure the 802.3ad is aggregating
properly; are all of the slaves in the active aggregator?
Lastly, what distro (cat /etc/issue) and kernel version are you
running (uname -a)?
I fixed a bug in 802.3ad related to aggregator assignments a
couple of weeks ago. If you've got a sufficiently recent kernel (the
bug was introduced late last year), you might be seeing that (if the
slaves don't aggregate properly). I observed the bug messing up 802.3ad
aggregations with my e1000 devices, so it might be that.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, [email protected]
------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
