Date: Thu, 04 May 2006 12:55:08 -0400 From: Mike Jakubik <mikej@rogers.com> To: "David G. Lawrence" <dg@dglawrence.com> Cc: marc@enginet.com, protagonist@gmx.net, freebsd-amd64@freebsd.org Subject: Re: nve(4) timeout fix Message-ID: <445A31EC.9080607@rogers.com> In-Reply-To: <20060504065909.GC12815@tnn.dglawrence.com> References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-868xppk0tz.fsf@shodan.gothgoose.net> <200604281646.46451.jhb@freebsd.org> <44528643.4050103@rogers.com> <4452A98E.8020501@samsco.org> <20060504065909.GC12815@tnn.dglawrence.com>
index | next in thread | previous in thread | raw e-mail
David G. Lawrence wrote: > It appears that the fix in -current isn't quite right in any case. A > friend of mine found that transmit interrupts don't appear to be occuring > at all. The only reason that the driver appears to work is that receive > packets/interrupts usually occur often enough so that the transmit > run-down still occurs often enough...except when it doesn't. If you > do a simple test of (only) sending UDP datagrams, for example, the driver > will eventually run out of buffers (or TX descriptors? - not sure which), > and the driver will be wedged up with no buffer space until a packet is > received (e.g. by a ping from another host). With the patch in current, > this reduces the no buffer space dead time to eight seconds (the watchdog > timeout), but that is still quite broken. > I don't have the documentation for the nve programming API, otherwise > I'd be tempted to try to figure out why it is broken. Maybe someone who > has access to that info can look into this? > Perhaps the nfe driver from openbsd would be a better choice. I believe someone posted a ported version on the list.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?445A31EC.9080607>