From owner-freebsd-net Mon Mar 3 18:24:46 2003 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 210CD37B401 for ; Mon, 3 Mar 2003 18:24:45 -0800 (PST) Received: from relay1.cris.net (relay1.cris.net [212.110.128.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 484FF43FBF for ; Mon, 3 Mar 2003 18:24:42 -0800 (PST) (envelope-from phantom@phantom.cris.net) Received: from phantom.cris.net (root@phantom.cris.net [212.110.130.74]) by relay1.cris.net (8.12.6/8.12.6) with ESMTP id h244Ycvb051056; Tue, 4 Mar 2003 04:34:38 GMT Received: (from phantom@localhost) by phantom.cris.net (8.12.6/8.12.2) id h242VV54042452; Tue, 4 Mar 2003 04:31:31 +0200 (EET) (envelope-from phantom) Date: Tue, 4 Mar 2003 04:31:30 +0200 From: Alexey Zelkin To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: maxsockbuf is useless value {?|:-(} Message-ID: <20030304043130.B42396@phantom.cris.net> References: <20030228130621.A16504@phantom.cris.net> <200302281931.h1SJVAUg060319@khavrinen.lcs.mit.edu> <20030301134118.GE77007@sunbay.com> <200303022015.h22KFbn0075585@khavrinen.lcs.mit.edu> <20030304040434.A42256@phantom.cris.net> <200303040212.h242C5fI001303@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200303040212.h242C5fI001303@khavrinen.lcs.mit.edu>; from wollman@lcs.mit.edu on Mon, Mar 03, 2003 at 09:12:05PM -0500 X-Operating-System: FreeBSD 4.7-STABLE i386 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 hi, On Mon, Mar 03, 2003 at 09:12:05PM -0500, Garrett Wollman wrote: > > As I stated originally, it's impossible to use 'maxsockbuf' value. > > That does not change the fact that an unprivileged user can use up to > `maxsockbuf' bytes of wired kernel memory per socket. That's why the > limit exists. The amount of memory allocated to socket buffer data > structures is not the same as the amount of user data which can be > stored in the socket buffer. Correct me if I wrong, but looks like since rev 1.102 of uipc_socket2.c "something" changed, and should be fixed in some way. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message