From owner-freebsd-net@FreeBSD.ORG Wed Feb 26 18:28:39 2014 Return-Path: Delivered-To: freebsd-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 ESMTPS id F04B2761 for ; Wed, 26 Feb 2014 18:28:39 +0000 (UTC) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9B42319C1 for ; Wed, 26 Feb 2014 18:28:38 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.97,549,1389765600"; d="scan'208";a="102402937" Message-ID: <530E3211.6020805@vangyzen.net> Date: Wed, 26 Feb 2014 12:27:29 -0600 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Sami Halabi , Subject: Re: TSO References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 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, 26 Feb 2014 18:28:40 -0000 On 02/26/2014 11:37, Sami Halabi wrote: > Hi, > I'm reading (almost) all mailing emails in mailig list... > > Almost every / many problem in network performancr / packets loss ended up > suggesting disabling TSO. > > I wonder why.. Is it a bug in the implementation? Or bybdesign? > What are the usecases that TSO is needed? Myabe it should be disabled bt > default? In some cases, I have disabled TSO to [successfully] work around a bug in a particular NIC's firmware or hardware, usually a low-end "desktop" gigabit NIC. Eric