From owner-freebsd-performance@FreeBSD.ORG Wed Jun 30 17:33:06 2004 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87C1A16A4CE for ; Wed, 30 Jun 2004 17:33:06 +0000 (GMT) Received: from mail.trippynames.com (mail.trippynames.com [216.143.148.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C28543D31 for ; Wed, 30 Jun 2004 17:33:06 +0000 (GMT) (envelope-from sean@chittenden.org) Received: from localhost (localhost [127.0.0.1]) by mail.trippynames.com (Postfix) with ESMTP id 664DEAAB97; Wed, 30 Jun 2004 10:32:54 -0700 (PDT) Received: from mail.trippynames.com ([127.0.0.1]) by localhost (rand.nxad.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02678-08; Wed, 30 Jun 2004 10:32:53 -0700 (PDT) Received: from [192.168.102.100] (dsl081-160-109.sea1.dsl.speakeasy.net [64.81.160.109]) by mail.trippynames.com (Postfix) with ESMTP id 164D6AAB86; Wed, 30 Jun 2004 10:32:53 -0700 (PDT) In-Reply-To: <40E2EF4D.3050508@t7ds.com.br> References: <40E1A47D.6020709@t7ds.com.br> <40E2EF4D.3050508@t7ds.com.br> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <83A6DC4F-CABB-11D8-B344-000A95C705DC@chittenden.org> Content-Transfer-Encoding: 7bit From: Sean Chittenden Date: Wed, 30 Jun 2004 10:32:52 -0700 To: fabulous X-Mailer: Apple Mail (2.618) cc: freebsd-performance@freebsd.org Subject: Re: net.inet.tcp.sendspace X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2004 17:33:06 -0000 > Thank you very very much.. but sysctl sendspace/recvspace will be the > limits then? Yes. > can I set SO_SNDBUF to something higher than tcp.sendspace? Hrm... tcp(4) is a bit ambiguous about this: MIB Variables The TCP protocol implements a number of variables in the net.inet.tcp branch of the sysctl(3) MIB. TCPCTL_SENDSPACE (sendspace) Maximum TCP send window. TCPCTL_RECVSPACE (recvspace) Maximum TCP receive window. I don't know if setsockopt(2) will allow you to exceed these values. I don't see anything in setsockopt(2) that suggests that you can't exceed TCPCTL_SENDSPACE with setsockopt(2). > I'm thinking of setting tcp.sendspace to 64k and using setsockopt on > ircd to set it to 2k (why an irc connection would need more than > that?), so apache will use 64k and ircd 2k.. am I right? :P This is a wise course of action given the uncertainty of setsockopt(2) and the net.inet.tcp.* interaction. I'd grep through the source and give you a definitive answer but am busy/too lazy at the moment. :) -sc -- Sean Chittenden