From owner-freebsd-hackers@FreeBSD.ORG  Sun Sep 11 13:08:12 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D875516A41F
	for <freebsd-hackers@freebsd.org>; Sun, 11 Sep 2005 13:08:12 +0000 (GMT)
	(envelope-from killing@multiplay.co.uk)
Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 453F943D45
	for <freebsd-hackers@freebsd.org>; Sun, 11 Sep 2005 13:08:11 +0000 (GMT)
	(envelope-from killing@multiplay.co.uk)
Received: from vader ([212.135.219.179])
	by multiplay.co.uk (multiplay.co.uk [85.236.96.23])
	(MDaemon.PRO.v8.1.1.R) with ESMTP id md50001809958.msg
	for <freebsd-hackers@freebsd.org>; Sun, 11 Sep 2005 14:07:40 +0100
Message-ID: <002901c5b6d1$c1c35030$b3db87d4@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: "Dan Nelson" <dnelson@allantgroup.com>
References: <003801c5b67e$f4c96120$b3db87d4@multiplay.co.uk>
	<20050911042242.GM84582@dan.emsphone.com>
Date: Sun, 11 Sep 2005 14:07:22 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2670
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Spam-Processed: multiplay.co.uk, Sun, 11 Sep 2005 14:07:40 +0100
	(not processed: message from valid local sender)
X-MDRemoteIP: 212.135.219.179
X-Return-Path: killing@multiplay.co.uk
X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org
X-MDAV-Processed: multiplay.co.uk, Sun, 11 Sep 2005 14:07:41 +0100
Cc: freebsd-hackers@freebsd.org
Subject: Re: setsockopt 228K fails with ERR#55 'No buffer space available'
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Sep 2005 13:08:13 -0000

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.