From owner-freebsd-current@FreeBSD.ORG Tue Oct 9 09:32:05 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 087A6D12 for ; Tue, 9 Oct 2012 09:32:05 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id AE3E28FC14 for ; Tue, 9 Oct 2012 09:32:04 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TLWAU-0003Tx-2y for freebsd-current@freebsd.org; Tue, 09 Oct 2012 11:32:02 +0200 Received: from broadband-77-37-234-86.nationalcablenetworks.ru ([77.37.234.86]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Oct 2012 11:32:02 +0200 Received: from vadim_nuclight by broadband-77-37-234-86.nationalcablenetworks.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Oct 2012 11:32:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Vadim Goncharov Subject: deprecation policy (Was: sysctl kern.ipc.somaxconn limit 65535 why?) Date: Tue, 9 Oct 2012 09:31:42 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 44 Message-ID: References: <03e101cda197$326dc240$974946c0$@org> <506C9CE4.6080400@freebsd.org> <20121008104934.GB25291@felucia.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: broadband-77-37-234-86.nationalcablenetworks.ru X-Comment-To: Jeremie Le Hen User-Agent: slrn/0.9.9p1 (FreeBSD) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2012 09:32:05 -0000 Hi Jeremie Le Hen! On Mon, 8 Oct 2012 12:49:34 +0200; Jeremie Le Hen wrote about 'Re: sysctl kern.ipc.somaxconn limit 65535 why?': >> On 03.10.2012 22:03, Adrian Chadd wrote: >>> >>> somaxconn is the connection queue depth. If it's sitting at a couple >>> hundred thousand then something else is going crazily wrong. >>> >>> I understand your frustration, but there's a lot of instances where >>> the application just isn't doing things "right" and the OS tries to >>> hide it as much as psosible. Blowing out somaxconn to chew up a whole >>> lot of resources seems a bit silly. I'd rather investigate why the >>> userland application is not servicing the connect queue often enough. >>> >>> I've written network services that supported tens of thousands of new >>> TCP connections a second on a LAN and I never once had to bump >>> somaxconn past 32767. I'm not saying that it won't apply to your >>> scenario, I'm just trying to explain that there's likely more going >>> on. >> >> I guess the problem is rather kern.ipc.maxsockets which is only 25600. >> >> The name somaxconn is confusing as it specifies the listen queue limit >> instead of the maximum number of connections as the it suggests. > If we want to change that name to something more sensible and less > error-prone like "somaxbacklog", does the project has a policy to change > sysctl names? > I'm thinking of something like renaming the sysctl to "somaxbacklog" and > make "somaxconn" compatibility shim during RELENG_10 which still works > but prints a warning in the dmesg. AFAIR, the policy was to keep for two major releases, not one, though it was the policy for binaries, not sysctl (e.g. if /sbin/natd would be officially made deprecated in 10.0 RELNOTES, then it must be kept in 10.* and 11.* with complete removal in 12.0). Possibly the policy for sysctl's is the same, because 3rd-party software may use such knobs, while not sure this applies to kern.*, though. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Anti-Greenpeace][Sober FreeBSD zealot][http://nuclight.livejournal.com]