netdev - RE: [PATCH NEXT 0/2] qlcnic: Add Qlogic 1/10Gb Ethernet driver for CNA devices

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7608421F3572AB4292BB2532AE89D5658B0BAE9411@AVEXMB1.qlogic.org>
Date:	Tue, 5 Jan 2010 11:02:00 -0800
From:	Dhananjay Phadke <dhananjay.phadke@...gic.com>
To:	Stephen Hemminger <shemminger@...tta.com>
CC:	Amit Salecha <amit.salecha@...gic.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH NEXT 0/2] qlcnic: Add Qlogic 1/10Gb Ethernet driver for
 CNA devices

> You should be doing GRO, what about multiple addresses per interface,
> bridging, routing, ...

We do GRO too (that helps when old firmware didn't support LRO).
Since all addresses associated with a net device are tracked
we do take care of IP aliases. Note that LRO packets are not
fed into GRO, although there's nothing that prevents it.

On older machines, GRO tops out CPU to get close to line rate,
LRO doesn't. Also, LRO reduces number of PCIe transactions.

LRO across bridge / routing is topology violation right?
We don't get inet notification for remote IP addresses (correct
me if wrong), so these cases are excluded from LRO.

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