netdev - Re: GRO aggregation

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: <5050B9B2.5070107@mellanox.com>
Date:	Wed, 12 Sep 2012 19:34:58 +0300
From:	Shlomo Pongartz <shlomop@...lanox.com>
To:	Rick Jones <rick.jones2@...com>
CC:	Eric Dumazet <eric.dumazet@...il.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: GRO aggregation

On 9/12/2012 7:23 PM, Rick Jones wrote:
> On 09/12/2012 07:41 AM, Shlomo Pongartz wrote:
>> Hi Eric
>>
>> The TSO is just a mean to create a burst of frames on the wire so the
>> NAPI will be able to pool as much as possible.
>
> Is it?  If I recall correctly, TSO was in place well before all 
> drivers were using NAPI.  And NAPI was being proposed independent of 
> TSO. TSO is there to save CPU cycles on the transmit side.  "On the 
> wire" what it sends is to be identical to what a host with greater CPU 
> performance could accomplish.
>
> rick jones
>
Hi Rick.

What I say is that I use TSO on the machine that transmits so I'll have  
a burst of frames on the wire for the NAPI on the receiver machine.
The best thing for my purpose is  that the HW will do the segmentation. 
And unless I'm mistaken the Intel card is capable to do so.

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