From owner-p4-projects@FreeBSD.ORG Thu Dec 7 16:30:54 2006 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id AC90516A49E; Thu, 7 Dec 2006 16:30:54 +0000 (UTC) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6DB8616A40F; Thu, 7 Dec 2006 16:30:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E9E844343; Thu, 7 Dec 2006 16:16:01 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F3E7646FA4; Thu, 7 Dec 2006 11:16:41 -0500 (EST) Date: Thu, 7 Dec 2006 16:16:41 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Paolo Pisati In-Reply-To: <20061207142254.GA1195@tin.it> Message-ID: <20061207161434.O50906@fledge.watson.org> References: <200612062319.kB6NJgsq031755@repoman.freebsd.org> <20061207110225.GU32700@FreeBSD.org> <4578070A.2030609@freebsd.org> <20061207142254.GA1195@tin.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Gleb Smirnoff , Andre Oppermann , Perforce Change Reviews Subject: Re: PERFORCE change 111230 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 16:30:54 -0000 On Thu, 7 Dec 2006, Paolo Pisati wrote: > Then, after a discussion on irc, pull the plug on any present (and future) > hackery & half-baked solution, and declare in kernel libalias incompatible > with tso. This seems silly -- why is it not compatible? Perhaps I misunderstand, but I thought TSO passed down valid TCP/IP packets, they just happen to be really long, and will be post-processed by the hardware into a series of shorter segments with the same header properties. Imagine the ethernet device as a "router" that's performing TCP fragmentation for you, rather than IP fragmentation. Robert N M Watson Computer Laboratory University of Cambridge