Date: Fri, 18 Oct 2002 11:31:08 +0300 From: "Petri Helenius" <pete@he.iki.fi> To: "Luigi Rizzo" <rizzo@icir.org> Cc: "Lars Eggert" <larse@ISI.EDU>, <freebsd-net@FreeBSD.ORG> Subject: Re: ENOBUFS Message-ID: <0d0b01c27680$b553ba90$8c2a40c1@PHE> References: <065901c27495$56a94c40$8c2a40c1@PHE> <3DAC8FAD.30601@isi.edu> <068b01c2749f$32e7cf70$8c2a40c1@PHE> <20021015161055.A27443@carp.icir.org> <06c901c274d8$e5280b80$8c2a40c1@PHE> <3DAD01A7.3020807@isi.edu> <071501c274db$222c3ea0$8c2a40c1@PHE> <3DAD06AF.7060701@isi.edu> <0be401c2761f$855af670$8c2a40c1@PHE> <20021017201158.A75351@carp.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > just reading the source code, yes, it appears that the card has > support for delayed rx/tx interrupts -- see RIDV and TIDV definitions > and usage in sys/dev/em/* . I don't know in what units are the values > (28 and 128, respectively), but it does appear that tx interrupts are > delayed a bit more than rx interrupts. > The thing what is looking suspect is also the "small packet interrupt" feature which does not seem to get modified in the em driver but is on the defines. If that would be on by default, weŽd probably see interrupts "too often" because it tries to optimize interrupts for good throughput on small number of TCP streams. Should these questions be posted to the authors of the driver? Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0d0b01c27680$b553ba90$8c2a40c1>