netdev - be2net: GRO for non-inet protocols

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130405132007.GF7551@eerihug-hybrid.ki.sw.ericsson.se>
Date:	Fri, 5 Apr 2013 15:20:07 +0200
From:	Erik Hugne <erik.hugne@...csson.com>
To:	sathya.perla@...lex.com, subbu.seetharaman@...lex.com,
	ajit.khaparde@...lex.com
CC:	netdev@...r.kernel.org
Subject: be2net: GRO for non-inet protocols

I'm adding GRO support for the TIPC protocol and
tried to test it on a pair of HP G7 blades with 
Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) NICs.

However, my GRO callback is never invoked on this setup, and 
i suspect the be2net driver is to blame.
I had a brief look at the driver, first suspecting that the
do_gro check only passed for inet protocols (tcpf must be set 
in the be_rx_compl_info struct).
However, removing this check did not change the behavior.

#ethtool -i eth1
driver: be2net
version: 4.4.161.0s
firmware-version: 4.1.450.7
bus-info: 0000:02:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: no

It works as expected on another setup with with Intel NIC's/e1000 driver.

//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