From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rick.jones2@hp.com>
Received: from g1t0028.austin.hp.com (g1t0028.austin.hp.com [15.216.28.35])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "smtp.hp.com",
	Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id D0C99201116
	for <bloat@lists.bufferbloat.net>; Fri, 13 Apr 2012 17:35:43 -0700 (PDT)
Received: from g1t0039.austin.hp.com (g1t0039.austin.hp.com [16.236.32.45])
	by g1t0028.austin.hp.com (Postfix) with ESMTP id 5E66A1C0A4;
	Sat, 14 Apr 2012 00:35:41 +0000 (UTC)
Received: from [16.89.64.213] (tardy.cup.hp.com [16.89.64.213])
	by g1t0039.austin.hp.com (Postfix) with ESMTP id 09D9334826;
	Sat, 14 Apr 2012 00:35:40 +0000 (UTC)
Message-ID: <4F88C65C.80209@hp.com>
Date: Fri, 13 Apr 2012 17:35:40 -0700
From: Rick Jones <rick.jones2@hp.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.28) Gecko/20120313 Lightning/1.0b2 Thunderbird/3.1.20
MIME-Version: 1.0
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
References: <20120406213725.GA12641@uio.no>
	<CAA93jw4ZrRo70uqAG2AOBcXxKmv0T8WFV34rAQSOnVZAk9-6Fw@mail.gmail.com>
	<20120406222138.GB12641@uio.no>
In-Reply-To: <20120406222138.GB12641@uio.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Best practices for paced TCP on Linux?
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Sat, 14 Apr 2012 00:35:44 -0000

On 04/06/2012 03:21 PM, Steinar H. Gunderson wrote:
> On Fri, Apr 06, 2012 at 02:49:38PM -0700, Dave Taht wrote:
>> However in your environment you will need the beefed up SFQ that is in 3.3.
>> and BQL. If you are not saturating that 10GigE card, you can turn off TSO/GSO
>> as well.
>
> We're not anywhere near saturating our 10GigE card, and even if we did, we
> could add at least one 10GigE card more.

TSO/GSO isn't so much about saturating the 10 GbE NIC as it is avoiding 
saturating the CPU(s) driving the 10 GbE NIC.  That is, they save trips 
down the protocol stack, saving CPU cycles.  So, if you are not 
saturating one or more of the CPUs in the system, disabling TSO/GSO 
should not affect your ability to drive bits out the NIC.

rick jones