On Wed, Jan 31, 2007 at 06:21:57PM +0100, Adriaan wrote: > On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote: > [snip] > > > >Running and tuning OpenBSD network servers > >in a production environment: > > > >http://www.openbsd.org/papers/tuning-openbsd.ps > > > >may have the info you're looking for. > > IIRC Theo said he would throw Henning in the ocean for that paper ;) >
Actually Henning said he would throw Henning in the ocean for that paper. But back to the original problem with the no buffer space reports. This is in fact an expected behaviour for non stream oriented protocols like udp or icmp (ping). The problem here is that ENOBUF is returned by the queuing code when the interface queue is full. The error is then reported upwards and in case of datagram sockets is reported back to the userland process. A smart client/server would reduce the packet throughput in such a case. e.g. ping -f is not that smart. In TCP this error is handled by the kernel and so mostly invisible for the userland. -- :wq Claudio
