From owner-freebsd-net@FreeBSD.ORG Wed Aug 14 00:51:24 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 94F6BCFF; Wed, 14 Aug 2013 00:51:24 +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 380BF220F; Wed, 14 Aug 2013 00:51:23 +0000 (UTC) Received: from jre-mbp.elischer.org (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.6) with ESMTP id r7E0pJh7014723 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 13 Aug 2013 17:51:21 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <520AD486.6050708@freebsd.org> Date: Wed, 14 Aug 2013 08:51:18 +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: Navdeep Parhar Subject: Re: TSO and FreeBSD vs Linux References: <520A6D07.5080106@freebsd.org> <520A6EC6.6050208@FreeBSD.org> In-Reply-To: <520A6EC6.6050208@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, 14 Aug 2013 00:51:24 -0000 On 8/14/13 1:37 AM, Navdeep Parhar wrote: > On 08/13/13 10:29, Julian Elischer wrote: > .. >> Has anyone done any work on aggregating ACKs, or delaying responding to >> them? > If LRO is enabled on the FreeBSD receiver, ACKs are already aggregated > (a duplicate ACK will result in an immediate flush though.) See tcp_lro_rx. not always, , certainly not with XEN (xn0) on EC2. > > Regards, > Navdeep >