Date: Sat, 7 Sep 1996 17:03:40 +0300 (AST) From: The ShadowS Know <shadows@whitefang.com> To: freebsd-questions@freebsd.org Subject: Buffer limit on socket Message-ID: <Pine.NEB.3.95.960907165923.1439H-100000@broken.whitefang.com>
next in thread | raw e-mail | index | archive | help
I'vr recently put together a program that eventually shoots out hundreds
of UDP packets for asynchronous DNS lookups. It worked fine on a number
of platforms my clients are using (SCO Unix, Linux etc), when I decided to
compile and test it on FreeBSD I wound up with one problem even though I
found a fix around, I'm just wondering why FreeBSD has it.
Basically after the hundred or so packet bieng shot I'd get
[ENOBUFS] The system was unable to allocate an internal buffer. The
operation may succeed when buffers become available.
(taken from the manpage)
I just had it wait for packets to arrive and then shoot out again. Seemed
to work fine. But this does slow it down a bit. Is there a way of
increasing my socket buffer size? I tried some socket options with no
result. It looks like an internal kernel socket allocation to me
(abviously). Is there a way of recompiling my kernel and increasing the
size? Like I could with descriptors and childproccesses per proccess?
-------------------------------------------------------------------------------
ShadowS WhiteFang Unix Software Development
Thamer Al-Herbish And Consultancy.
shadows@whitefang.com
Specialising in Custom Network Applications
for Unix Systems.
-------------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.960907165923.1439H-100000>