From owner-freebsd-net@FreeBSD.ORG Fri Aug 23 08:21:40 2013 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 11259629; Fri, 23 Aug 2013 08:21:40 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D83C42565; Fri, 23 Aug 2013 08:21:39 +0000 (UTC) Received: from Julian-MBP3.local (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.6) with ESMTP id r7N8LZcd091429 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 01:21:38 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52171B89.8030602@freebsd.org> Date: Fri, 23 Aug 2013 16:21:29 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Andre Oppermann Subject: Re: TSO and FreeBSD vs Linux References: <520A6D07.5080106@freebsd.org> <5214F506.3070706@freebsd.org> In-Reply-To: <5214F506.3070706@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: Fri, 23 Aug 2013 08:21:40 -0000 On 8/22/13 1:12 AM, Andre Oppermann wrote: > 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. > yes we have those fixes.