From owner-freebsd-current@FreeBSD.ORG Thu Aug 16 22:23:07 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0D0316A419 for ; Thu, 16 Aug 2007 22:23:07 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 9842513C467 for ; Thu, 16 Aug 2007 22:23:07 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id 7714E10FAB; Thu, 16 Aug 2007 17:04:37 -0500 (CDT) Date: Thu, 16 Aug 2007 17:04:36 -0500 From: Craig Boston To: Kip Macy Message-ID: <20070816220427.GA6457@nowhere> Mail-Followup-To: Craig Boston , Kip Macy , Andrew Gallatin , freebsd-current@freebsd.org References: <18116.43755.107638.103132@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, Andrew Gallatin Subject: Re: IPSEC disables TSO X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2007 22:23:07 -0000 On Thu, Aug 16, 2007 at 12:53:46PM -0700, Kip Macy wrote: > IPSEC encrypts the TCP header - how is the card going to do TSO? Maybe I'm missing something, but I don't understand why IPSEC should have to disable TSO at all. Of course encrypted packets won't be able to take advantage of TSO, but by the time they reach the NIC, they're not TCP anymore. They're IP protocol 50 (ESP). Shouldn't TSO simply be ignoring protocols other than TCP? Craig