netdev - RE: Question on TSO maximum segment sizes.

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]

Message-ID: <D5C1322C3E673F459512FB59E0DDC32903C440EE@orsmsx414.amr.corp.intel.com>
Date:	Thu, 11 Oct 2007 17:06:11 -0700
From:	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
To:	"David Miller" <davem@...emloft.net>, <rick.jones2@...com>
Cc:	<netdev@...r.kernel.org>
Subject: RE: Question on TSO maximum segment sizes.

> From: Rick Jones <rick.jones2@...com>
> Date: Thu, 11 Oct 2007 16:50:46 -0700
> 
> > For just messing about, might it be possible to tweak the socket 
> > buffer sizes and tcp_tso_win_divisor to kludge things for a short 
> > while?  Couldn't ship that way certainly, but assuming 
> Peter's going 
> > to get his broken hardware fixed it might let him limp 
> along until then.
> 
> TCP dynamically grows the socket buffer sizes unless the 
> application explicitly sets them via setsockopt() and the 
> limits imposed in those cases are controlled by 
> tcp_{,r,w}mem[] sysctls.  Decreasing those will kill 
> performance exactly for the cases this person cares about.
> 
> No, the only way to deal with this is to GSO segment incoming 
> frames inside of the driver when they exceed the HW limits.

Thanks Dave and Rick.  I'll mess with this and make my driver happy
again.

Cheers,
-PJ Waskiewicz
-
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