nve(4) timeout fix

Mike Jakubik mikej at rogers.com
Thu May 4 16:55:20 UTC 2006


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.



More information about the freebsd-amd64 mailing list