Date: Sun, 11 Sep 2005 14:07:22 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Dan Nelson" <dnelson@allantgroup.com> Cc: freebsd-hackers@freebsd.org Subject: Re: setsockopt 228K fails with ERR#55 'No buffer space available' Message-ID: <002901c5b6d1$c1c35030$b3db87d4@multiplay.co.uk> References: <003801c5b67e$f4c96120$b3db87d4@multiplay.co.uk> <20050911042242.GM84582@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks dan but I already tried that and it doesn't work but maxsockbuf
does. Really looking for the affects that altering that might have and
if its a good idea. 256k send and receive buffers on a socket seem
very large to me.
Steve
----- Original Message -----
From: "Dan Nelson" <dnelson@allantgroup.com>
> In the last episode (Sep 11), Steven Hartland said:
>> The following fails with ERR#55 'No buffer space available'
>> int buf_size = (228*1024);
>> int ret = setsockopt( s, SOL_SOCKET, SO_SNDBUF, (void*) &buf_size, sizeof(
>> buf_size ) );
>>
>> This appears like its controlled by kern.ipc.maxsockbuf which is
>> default of 256k so the above should work if its per socket and not
>> total?
>
> I think you want net.inet.tcp.sendspace; kern.ipc.maxsockbuf seems to
> be unused based on a quick grep of the source.
>
> Also check the sockbufsize rlimit, although I think that defaults to
> unlimited.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002901c5b6d1$c1c35030$b3db87d4>