From owner-freebsd-current@FreeBSD.ORG Wed Sep 13 05:37:50 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B851C16A40F; Wed, 13 Sep 2006 05:37:50 +0000 (UTC) (envelope-from if@hetzner.co.za) Received: from hetzner.co.za (office.cpt2.host-h.net [196.7.147.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1B1A43D46; Wed, 13 Sep 2006 05:37:49 +0000 (GMT) (envelope-from if@hetzner.co.za) Received: from localhost ([127.0.0.1] helo=ian.hetzner.africa) by hetzner.co.za with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GNNRO-000BKY-S1; Wed, 13 Sep 2006 07:37:42 +0200 To: "Jack Vogel" From: Ian FREISLICH In-Reply-To: Message from "Jack Vogel" of "Tue, 12 Sep 2006 17:59:24 MST." <2a41acea0609121759l4684b047r350fb0763d0ccc84@mail.gmail.com> X-Attribution: BOFH Date: Wed, 13 Sep 2006 07:37:42 +0200 Message-Id: Cc: Andre Oppermann , current@freebsd.org, Mike Tancsa Subject: Re: TSO, SMP and the em driver. 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: Wed, 13 Sep 2006 05:37:50 -0000 "Jack Vogel" wrote: > On 9/12/06, Andre Oppermann wrote: > > Mike Tancsa wrote: > > > At 12:43 PM 9/12/2006, Andre Oppermann wrote: > > > > > >> TSO != (vlan && promisc) > > > > > > Sorry, the commonality I was referring to was VLAN hardware tagging and > > > how it must be enabled for TSO, but that breaks other things. See a few > > > messages ago > > > http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065818.html > > > > I'm sure we can find a workaround for that. > > Not sure what you are referring to Andre, working around which part? EM + CARP + VLAN + TSO is an unworkable combination since VLANHWTAG gets broken by PROMISC required by CARP. TSO requires VLANHWTAG. Is the VLANHWTAG + PROMISC problem a driver or hardware problem? Ian -- Ian Freislich