Date: Fri, 11 Jun 2010 13:18:17 -0700 From: Jack Vogel <jfvogel@gmail.com> To: "Bjoern A. Zeeb" <bz@freebsd.org> Cc: Jack F Vogel <jfv@freebsd.org>, svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r209060 - head/sys/dev/ixgbe Message-ID: <AANLkTim0tKu-Ul1SpadatFJm994pmZbDxvw2GpuUkWVV@mail.gmail.com> In-Reply-To: <20100611200936.B26508@maildrop.int.zabbadoz.net> References: <201006111903.o5BJ3xp1062600@svn.freebsd.org> <20100611193903.W26508@maildrop.int.zabbadoz.net> <AANLkTimic2IcWP-vI21gehFAbFKbqzUtpmvVnd2r_hLY@mail.gmail.com> <20100611200936.B26508@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Odd though, because that code is in the driver on a system with 16 cores and I'm not hearing about any problem from my test engineer. Jack On Fri, Jun 11, 2010 at 1:13 PM, Bjoern A. Zeeb <bz@freebsd.org> wrote: > On Fri, 11 Jun 2010, Jack Vogel wrote: > > Hi, > > > HMMMMM, I put in a change in response to some people having problems with >> mbuf resources, it seemed to work ok, but now i'm kinda concerned. Does >> this >> happen every time you bring the device up? >> >> In the routine 'ixgbe_setup_receive_ring()' I changed a couple of >> M_NOWAIT's >> to M_WAITOK, thinking that it would be ok in this code, can you test it, >> change >> it back to M_NOWAIT, and see if this symptom goes away? >> > > Will do and let you know. > > I assume you mean the ones as part of r208762? > > > > How many cores does the machine have, I'm guessing its big? >> > > 4 > > After ~890 of those tires, locks, abd backtraces deadlkres killed it;) > > /bz >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim0tKu-Ul1SpadatFJm994pmZbDxvw2GpuUkWVV>