From owner-freebsd-net Wed Mar 20 14:33:51 2002 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 2CC0D37B400 for ; Wed, 20 Mar 2002 14:33:45 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.6) id g2KMXcC61425; Wed, 20 Mar 2002 17:33:38 -0500 (EST) (envelope-from wollman) Date: Wed, 20 Mar 2002 17:33:38 -0500 (EST) From: Garrett Wollman Message-Id: <200203202233.g2KMXcC61425@khavrinen.lcs.mit.edu> To: Mike Silbersack Cc: net@FreeBSD.ORG Subject: Re: Getting rid of maxsockets. In-Reply-To: <20020320145723.X55299-100000@patrocles.silby.com> References: <200203202026.g2KKQch60289@khavrinen.lcs.mit.edu> <20020320145723.X55299-100000@patrocles.silby.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > That would end up being a reduction below the current value; right now > sockets > maxfiles with large maxuser values. Whether or not this is a > necessary differential, I'm not sure. (With TIME_WAIT and FIN_WAIT_2 > sockets, I believe that maxsockets should exceed maxfiles.) My point was that it's not necessary to enforce a limit on sockets, specifically, because maxfiles (and user resource limits) will keep users from opening too many sockets. We should probably look to templating closed TCP connections, since they don't actually need a socket at all (or most of the PCB). -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message