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-next>] [day] [month] [year] [list]
Message-ID: <de0a9dcb1002280900k728b241fyd72112defc0336ea@mail.gmail.com>
Date:	Sun, 28 Feb 2010 22:30:24 +0530
From:	raj ravi <mekaviraj@...il.com>
To:	netdev@...r.kernel.org
Subject: GSO / TSO offload dependency

Hi,
I m currently working on TSO feature in Linux network driver.

Please correct my understanding.

GSO - Generic segmentation offload - does not require any hardware support.

TSO - TCP segmentation offload  - does require hardward support


Does TSO needs GSO to be turned on?  OR in other words,  can I have
GSO disabled and TSO Enabled ?
I beleive the code is tied between both offload...but not sure about
the above possibility... please clarify.


Just before handing over the packets to the Network driver,
segmentation is carried out a call to dev_gso_segment ( ) function.
Given GSO is enabled, It will take care about creating TCP and other
protocol  segments  too,  even if TSO is disabled.. ..correct ?

If hardware supports TSO, and  If TSO and GSO are both enabled, ...
what will happen to segmentation assembly by means of GSO ...
GSO will not do any segmentatoin assembly for TCP alone and will do
for other protocols ??  bit confused here? Please clarify.

Thx!
Kavi
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ