Date: Mon, 17 Oct 2011 23:59:50 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Ben Hutchings <bhutchings@solarflare.com> Cc: freebsd-net@freebsd.org, Andre Oppermann <andre@freebsd.org> Subject: Re: TSO broken with jumbo MTU Message-ID: <68546593-B3E1-44D8-B512-4FD99B90D989@lists.zabbadoz.net> In-Reply-To: <1318894136.2784.76.camel@bwh-desktop> References: <1317309906.2743.9.camel@bwh-desktop> <1318865394.2784.4.camel@bwh-desktop> <4E9C534D.4090405@freebsd.org> <1318894136.2784.76.camel@bwh-desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17. Oct 2011, at 23:28 , Ben Hutchings wrote:
> On Mon, 2011-10-17 at 18:09 +0200, Andre Oppermann wrote:
>> On 17.10.2011 17:29, Ben Hutchings wrote:
>>> This is the fix/workaround I used:
>>
>> Thanks for the fix. I'll review it and put it into FreeBSD maybe in
>> a slightly different form.
>
> Which one? One is tested but maybe not right; the other looks right but
> is not tested!
and here's the real question -- was it always broken or did a commit during
the last years introduce the problem?
--
Bjoern A. Zeeb You have to have visions!
Stop bit received. Insert coin for new address family.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?68546593-B3E1-44D8-B512-4FD99B90D989>