From owner-freebsd-net@FreeBSD.ORG Fri Mar 29 15:57:32 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AC4A4146 for ; Fri, 29 Mar 2013 15:57:32 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from nm32-vm5.bullet.mail.ne1.yahoo.com (nm32-vm5.bullet.mail.ne1.yahoo.com [98.138.229.53]) by mx1.freebsd.org (Postfix) with ESMTP id 78290D0B for ; Fri, 29 Mar 2013 15:57:32 +0000 (UTC) Received: from [98.138.90.51] by nm32.bullet.mail.ne1.yahoo.com with NNFMP; 29 Mar 2013 15:54:09 -0000 Received: from [98.138.89.234] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 29 Mar 2013 15:54:09 -0000 Received: from [127.0.0.1] by omp1049.mail.ne1.yahoo.com with NNFMP; 29 Mar 2013 15:54:09 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 440903.45602.bm@omp1049.mail.ne1.yahoo.com Received: (qmail 52944 invoked by uid 60001); 29 Mar 2013 15:54:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1364572449; bh=ER2VkXX49TOajnjx/SObF/5r5r7we+9k4XN+G1pxp04=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Guuu58qUd6otnlzrUXoFZzrvETYmAguXnYcuNsO9OJXXHCiTWE8PGJ8598PqoqgTBocBx/+R9DUyCz3Sm6VC/+LCgqcNAjO/AyJKabozkWgzsW2RlVBlYQIIXGOlo4ghJhl/4SrFqOAKlUqV41VWjtH0koBa+VlUK+LHu/LbX4k= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PvRWv/WtG8ezJvRBQzc5rHMqxqFRctS6/DWUYTfNx3v2l3E1WjGzO7lMmP2jCqwtHNCagnH57c9NaurTeAnEbU/kbGLAMQ56ceSQIMAS89r7jlDF/urEk68OWJZbfJ+d3wZB2+vnLm72J6RNo3Zyqsa7/xk/hcEnJm5SakzkTrg=; X-YMail-OSG: P4Amp8MVM1nDm5biCjEtn1U.7t43idvOC.PRSwYEhya1Pag 92Ku_ZqsppoU.IRpkUpvXtfVAtrhPw.Bdl2bxkd4Fv1FCX7q.LRXkY5J_TVg dZvbHP.8LMknjQrJEqqyMTnxkhVlqG8X0o4l7h8M8aMo0FjrjS8EPECCjnV0 I3zZTInVB63v.T3sfE7RAQK_kzDfRCvKVPAfoyaRUndjDaAYwwd6e_ggYgNl M2Ab1nAiH.0E1l5ZwBBVCRpLNp98ufbPvmmvmyKuIrjH4RFAn8gQiC3JuqGU 0EV3RGg9OfUbS7Slmv6qTQjYQp073VqpT_yAw1gvlAgBYUmCaoqtrPUdGOG9 ylgcAfLDIr1yw0nNoDuWIJXNZVxYSHpMFAQldndIRi5GdR.1_tWSzmZ5wPXf a1VInirdY2CDHY1QOTfBxgCLpJrv0Ldlh5tXJg7kzQmm3Kvecd7N4THY7I35 Jhc4suoGsEjUBRBal1zQ24T.uXd6fgYPEDVYIYuNeSauoSBh91gInuMZfdVp l4Uit.NfEwIVpUtW1H2HDUsArKZoWFw-- Received: from [98.203.118.124] by web121605.mail.ne1.yahoo.com via HTTP; Fri, 29 Mar 2013 08:54:08 PDT X-Rocket-MIMEInfo: 002.001, CgotLS0gT24gRnJpLCAzLzI5LzEzLCBQaWVwZXIsIEplZmZyZXkgRSA8amVmZnJleS5lLnBpZXBlckBpbnRlbC5jb20.IHdyb3RlOgoKPiBGcm9tOiBQaWVwZXIsIEplZmZyZXkgRSA8amVmZnJleS5lLnBpZXBlckBpbnRlbC5jb20.Cj4gU3ViamVjdDogUkU6IGlnYiBhbmQgQUxUUSBpbiA5LjEtcmMzCj4gVG86ICJCYXJuZXkgQ29yZG9iYSIgPGJhcm5leV9jb3Jkb2JhQHlhaG9vLmNvbT4sICJKYWNrIFZvZ2VsIiA8amZ2b2dlbEBnbWFpbC5jb20.LCAiTmljayBSb2dlcnMiIDxuY3JvZ2Vyc0BnbWFpbC5jb20BMAEBAQE- X-Mailer: YahooMailClassic/15.1.7 YahooMailWebService/0.8.139.530 Message-ID: <1364572448.52354.YahooMailClassic@web121605.mail.ne1.yahoo.com> Date: Fri, 29 Mar 2013 08:54:08 -0700 (PDT) From: Barney Cordoba Subject: RE: igb and ALTQ in 9.1-rc3 To: Jack Vogel , Nick Rogers , Jeffrey EPieper In-Reply-To: <2A35EA60C3C77D438915767F458D65687D46B19E@ORSMSX101.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "freebsd-net@freebsd.org" , "Clement Hermann \(nodens\)" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Mar 2013 15:57:32 -0000 --- On Fri, 3/29/13, Pieper, Jeffrey E wrote: > From: Pieper, Jeffrey E > Subject: RE: igb and ALTQ in 9.1-rc3 > To: "Barney Cordoba" , "Jack Vogel" , "Nick Rogers" > Cc: "freebsd-net@freebsd.org" , "Clement Hermann (nodens)" > Date: Friday, March 29, 2013, 11:45 AM > > > -----Original Message----- > From: owner-freebsd-net@freebsd.org > [mailto:owner-freebsd-net@freebsd.org] > On Behalf Of Barney Cordoba > Sent: Friday, March 29, 2013 5:51 AM > To: Jack Vogel; Nick Rogers > Cc: freebsd-net@freebsd.org; > Clement Hermann (nodens) > Subject: Re: igb and ALTQ in 9.1-rc3 > > > > --- On Thu, 3/28/13, Nick Rogers > wrote: > > > From: Nick Rogers > > Subject: Re: igb and ALTQ in 9.1-rc3 > > To: "Jack Vogel" > > Cc: "Barney Cordoba" , > "Clement Hermann (nodens)" , > "freebsd-net@freebsd.org" > > > Date: Thursday, March 28, 2013, 9:29 PM > > On Thu, Mar 28, 2013 at 4:16 PM, Jack > > Vogel > > wrote: > > > Have been kept fairly busy with other matters, > one > > thing I could do short > > > term is > > > change the defines in igb the way I did in the em > > driver so you could still > > > define > > > the older if_start entry. Right now those are > based on > > OS version and so you > > > will > > > automatically get if_transmit, but I could change > it to > > be IGB_LEGACY_TX or > > > so, > > > and that could be defined in the Makefile. > > > > > > Would this help? > > > > I'm currently using ALTQ successfully with the em > driver, so > > if igb > > behaved the same with respect to using if_start instead > of > > if_transmit > > when ALTQ is in play, that would be great. I do not > > completely > > understand the change you propose as I am not very > familiar > > with the > > driver internals. Any kind of patch or extra > > Makefile/make.conf > > definition that would allow me to build a 9-STABLE > kernel > > with an igb > > driver that works again with ALTQ, ASAP, would be much > > appreciated. > > > > > > > > Jack > > > > > > > > > > > > On Thu, Mar 28, 2013 at 2:31 PM, Nick Rogers > > > wrote: > > >> > > >> On Tue, Dec 11, 2012 at 1:09 AM, Jack Vogel > > > wrote: > > >> > On Mon, Dec 10, 2012 at 11:58 PM, Gleb > > Smirnoff > > >> > wrote: > > >> > > > >> >> On Mon, Dec 10, 2012 at 03:31:19PM > -0800, > > Jack Vogel wrote: > > >> >> J> UH, maybe asking the owner of > the > > driver would help :) > > >> >> J> > > >> >> J> ... and no, I've never been > aware of > > doing anything to stop > > >> >> supporting > > >> >> altq > > >> >> J> so you wouldn't see any > commits. If > > there's something in the altq > > >> >> code > > >> >> or > > >> >> J> support (which I have nothing > to do > > with) that caused this no-one > > >> >> informed > > >> >> J> me. > > >> >> > > >> >> Switching from if_start to > if_transmit > > effectively disables ALTQ > > >> >> support. > > >> >> > > >> >> AFAIR, there is some magic > implemented in > > other drivers that makes them > > >> >> modern (that means using > if_transmit), but > > still capable to switch to > > >> >> queueing > > >> >> mode if SIOCADDALTQ was casted upon > them. > > >> >> > > >> >> > > >> > Oh, hmmm, I'll look into the matter after > my > > vacation. > > >> > > > >> > Jack > > >> > > >> Has there been any progress on resolving this > > issue? I recently ran > > >> into this problem upgrading my servers from > 8.3 to > > 9.1-RELEASE and am > > >> wondering what the latest recommendation is. > I've > > used ALTQ and igb > > >> successfully for years and it is unfortunate > it no > > longer works. > > >> Appreciate any advice. > > >> > > > >Do yourself a favor and either get a cheap dual port > 82571 card or > >2 cards and disable the IGB ports. The igb driver is > defective, and until > >they back out the new, untested multi-queue stuff you're > just neutering > >your system trying to use it. > > > >Frankly this project made a huge mistake by moving > forward with multi > >queue just for the sake of saying that you support it; > without having > >any credible plan for implementing it. That nonsense > that Bill Macy did > >should have been tarballed up and deposited in the trash > folder. The > >biggest mess in programming history. > > > >That being said, the solution is not to hack the igb > driver; its to make > >ALTQ if_transmit compatible, which shouldn't be all that > difficult. > > > >BC > > I may be misunderstanding what you are saying, but if the > solution is, as you say "not to hack the igb driver", then > how is it defective in this case? Or are you just directing > vitriol toward Intel? Multi-queue is working fine in igb. > > Jeff It's defective because it's been poorly implemented and has more bugs than a Manhattan hotel bed. Adding queues without a proper plan just add more lock contention. It's not a production-ready driver. As Jack once said, Intel doesn't care about performance, they're just example drivers. igb is an example of how not to do things. BC