netdev - Re: [net-next PATCH 1/3] ixgbe: enable HW RSC for 82599

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 29 Apr 2009 09:16:48 -0700
From:	Alexander Duyck <alexander.h.duyck@...el.com>
To:	David Miller <davem@...emloft.net>
CC:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"gospo@...hat.com" <gospo@...hat.com>
Subject: Re: [net-next PATCH 1/3] ixgbe: enable HW RSC for 82599

David Miller wrote:
> From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
> Date: Tue, 28 Apr 2009 17:12:10 -0700 (Pacific Daylight Time)
> 
>> ah, you're right, but this features enables our new hardware that can do 
>> LRO in hardware, and then GRO can work on top of it if necessary.  We 
>> wanted some way to turn it off and overloaded the LRO flag to do so.
> 
> That ugly.  And the kernel is going to turn this off on you
> when the user enables either forwarding or bridging.

That would likely be a desirable consequence.  If the interface is used 
for forwarding or bridging we probably would want to turn the feature 
off since it has many of the same limitations as software LRO.  Then we 
can let software GRO take over and handle all of the coalescing.

Thanks,

Alex



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