[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130424074433.GM18628@eerihug-hybrid.ki.sw.ericsson.se>
Date: Wed, 24 Apr 2013 09:44:33 +0200
From: Erik Hugne <erik.hugne@...csson.com>
To: "Bandi,Sarveshwar" <Sarveshwar.Bandi@...lex.Com>
CC: Eric Dumazet <eric.dumazet@...il.com>,
"Perla, Sathya" <Sathya.Perla@...lex.Com>,
"Seetharaman, Subramanian" <subbu.seetharaman@...lex.com>,
"Khaparde, Ajit" <Ajit.Khaparde@...lex.Com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: be2net: GRO for non-inet protocols
I got my hands on some new hardware with Intel 82599EB based 10G nics
(Ixgbe driver)
TIPC GRO works fine with this, the 256b segments sent over a stream connection
are aggregated together as shown below.
[...]
09:24:36.640506 3c:19:7d:0f:de:44 (oui Unknown) > 3c:19:7d:10:1e:68 (oui Unknown), Unknown Ethertype (0x88ca), length 6950:
09:24:36.640610 3c:19:7d:0f:de:44 (oui Unknown) > 3c:19:7d:10:1e:68 (oui Unknown), Unknown Ethertype (0x88ca), length 10534:
09:24:36.640775 3c:19:7d:0f:de:44 (oui Unknown) > 3c:19:7d:10:1e:68 (oui Unknown), Unknown Ethertype (0x88ca), length 18470:
09:24:36.640863 3c:19:7d:0f:de:44 (oui Unknown) > 3c:19:7d:10:1e:68 (oui Unknown), Unknown Ethertype (0x88ca), length 2598:
[...]
This confirms that the problem is in be2net driver and/or firmware.
//E
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists