Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Sep 2005 23:22:42 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Steven Hartland <killing@multiplay.co.uk>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: setsockopt 228K fails with ERR#55 'No buffer space available'
Message-ID:  <20050911042242.GM84582@dan.emsphone.com>
In-Reply-To: <003801c5b67e$f4c96120$b3db87d4@multiplay.co.uk>
References:  <003801c5b67e$f4c96120$b3db87d4@multiplay.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
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.

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050911042242.GM84582>