From owner-freebsd-stable@FreeBSD.ORG Wed May 16 18:15:31 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 91F1616A401 for ; Wed, 16 May 2007 18:15:31 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [216.148.227.151]) by mx1.freebsd.org (Postfix) with ESMTP id 7DC8B13C44C for ; Wed, 16 May 2007 18:15:31 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-71-198-0-135.hsd1.ca.comcast.net[71.198.0.135]) by comcast.net (rwcrmhc11) with ESMTP id <20070516181530m11006funpe>; Wed, 16 May 2007 18:15:31 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id A89091FA020; Wed, 16 May 2007 11:15:30 -0700 (PDT) Date: Wed, 16 May 2007 11:15:30 -0700 From: Jeremy Chadwick To: Tom Judge Message-ID: <20070516181530.GA48926@icarus.home.lan> Mail-Followup-To: Tom Judge , Jack Vogel , FreeBSD Stable List References: <2a41acea0705161030k40831aa5o168b5bc40fcf3352@mail.gmail.com> <464B48EB.20906@tomjudge.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <464B48EB.20906@tomjudge.com> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: FreeBSD Stable List , Jack Vogel Subject: Re: EM and TSO X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2007 18:15:31 -0000 On Wed, May 16, 2007 at 07:09:47PM +0100, Tom Judge wrote: > Jack Vogel wrote: > > I introduced a change yesterday that limited TSO to PCI Express > > adapters, I did this more for avoidance rather than a bug fix, and > > I'm not 100% sure its the right thing, so I thought I would poll > > everyone, do you have a PCI-X adapter and are using TSO without > > problems and wish to keep the support in? > > If no one is then I'll just leave it as is. > > Jack This is for Jack: Did you mean PCI Express instead of PCI-X in your latter sentence? PCI Express != PCI-X. If you did mean PCI-X, then I would assume the change could also affect standard PCI devices... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |