From owner-freebsd-net@FreeBSD.ORG  Thu May 31 00:09:35 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id F337016A469
	for <freebsd-net@freebsd.org>; Thu, 31 May 2007 00:09:34 +0000 (UTC)
	(envelope-from thompsa@FreeBSD.org)
Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz
	[203.109.251.39])
	by mx1.freebsd.org (Postfix) with ESMTP id A444513C458
	for <freebsd-net@freebsd.org>; Thu, 31 May 2007 00:09:34 +0000 (UTC)
	(envelope-from thompsa@FreeBSD.org)
Received: by heff.fud.org.nz (Postfix, from userid 1001)
	id EC3B11CC5A; Thu, 31 May 2007 11:54:56 +1200 (NZST)
Date: Thu, 31 May 2007 11:54:56 +1200
From: Andrew Thompson <thompsa@FreeBSD.org>
To: Jack Vogel <jfvogel@gmail.com>
Message-ID: <20070530235456.GA67464@heff.fud.org.nz>
References: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2a41acea0705301645x65e68e8q23c1b91d5f460ea3@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: freebsd-net <freebsd-net@freebsd.org>
Subject: Re: driver packet coalesce
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2007 00:09:35 -0000

On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote:
> Does any driver do this now? And if a driver were to coalesce
> packets and send something up the stack that violates mss
> will it barf?

It would barf for things like bridging where the packet gets spit out a
different interface. The bridge driver already has code to disable
txcsum so it could be made to handle that too.


Andrew