netdev - Re: behavior of TSO in kernel

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

Message-ID: <Pine.LNX.4.64.0906091052080.31791@melkinkari.cs.Helsinki.FI>
Date:	Tue, 9 Jun 2009 11:01:55 +0300 (EEST)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	Radha Mohan <radhamohan_ch@...oo.com>
cc:	Netdev <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>
Subject: Re: behavior of TSO in kernel

On Sat, 6 Jun 2009, Radha Mohan wrote:

> >The TSO engine of the networking has been rewritten at least
> >3 times since 2.6.15
> Thank you for the info.
> Actually we are working on an SoC and we just started moving from kernel 
> 2.6.15, so can you tell me from which kernel version the latest TSO 
> engine is being used. That'll make our life easier and avoid moving 
> kernels frequently. Currently we are thinking of moving to 2.6.24. Will 
> that do??   

There are at least some fixes since that time too... Besides, I'd 
recommend you staying away from 2.6.24 anyway because it is rather
broken on TCP side too (and was already obsolete when the problem was 
discovered so it was never fixed)...

What is the problem in starting with a very recent kernel such as the 
almost released 2.6.30 or the current stable 2.6.29? Another alternative 
you might want to consider the long supported version 2.6.27 (IIRC, check 
the archives whether it was .27 or .28). However, if there's even 
a slightest consideration of submitting your changes into mainline, the
latest is the best choice, and keeping up with the upstream during the 
development is certainly my recommendation too (with git it should be 
rather straightforward to handle that).

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