From owner-freebsd-net@FreeBSD.ORG Wed Aug 21 17:12:45 2013 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C85D3C38 for ; Wed, 21 Aug 2013 17:12:45 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 357862AB5 for ; Wed, 21 Aug 2013 17:12:44 +0000 (UTC) Received: (qmail 73225 invoked from network); 21 Aug 2013 17:55:48 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 21 Aug 2013 17:55:48 -0000 Message-ID: <5214F506.3070706@freebsd.org> Date: Wed, 21 Aug 2013 19:12:38 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Julian Elischer Subject: Re: TSO and FreeBSD vs Linux References: <520A6D07.5080106@freebsd.org> In-Reply-To: <520A6D07.5080106@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Aug 2013 17:12:45 -0000 On 13.08.2013 19:29, Julian Elischer wrote: > I have been tracking down a performance embarrassment on AMAZON EC2 and have found it I think. > Our OS cousins over at Linux land have implemented some interesting behaviour when TSO is in use. There used to be a different problem with EC2 and FreeBSD TSO. The Xen hypervisor doesn't like large 64K TSO bursts we generate, the drivers drops the whole TSO chain, TCP gets upset and turns off TSO alltogether leaving the connection going at one packet a time as in the old days. The problem is already fixed in recent EC2 9-stable images provided by cperciva. -- Andre