Date: Tue, 4 Mar 2003 04:04:34 +0200
From: Alexey Zelkin <phantom@FreeBSD.org.ua>
To: Garrett Wollman <wollman@lcs.mit.edu>
Cc: Ruslan Ermilov <ru@FreeBSD.ORG>, freebsd-net@FreeBSD.ORG
Subject: Re: maxsockbuf is useless value {?|:-(}
Message-ID: <20030304040434.A42256@phantom.cris.net>
In-Reply-To: <200303022015.h22KFbn0075585@khavrinen.lcs.mit.edu>; from wollman@lcs.mit.edu on Sun, Mar 02, 2003 at 03:15:37PM -0500
References: <20030228130621.A16504@phantom.cris.net> <200302281931.h1SJVAUg060319@khavrinen.lcs.mit.edu> <20030301134118.GE77007@sunbay.com> <200303022015.h22KFbn0075585@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, On Sun, Mar 02, 2003 at 03:15:37PM -0500, Garrett Wollman wrote: > <<On Sat, 1 Mar 2003 15:41:18 +0200, Ruslan Ermilov <ru@FreeBSD.ORG> said: > > > Seriously, you didn't give any alternative. How does one > > knows the maximum allowed limit? By just blindly trying? > > Ask for however much you think you actually need, and bleat to the > administrator (or limp along) if you don't get it. Keep in mind that > this is a security-sensitive parameter (a user can use up to > `maxsockbuf' bytes of wired kernel memory for each file descriptor he > is allowed to open). Wrong. As I stated originally, it's impossible to use 'maxsockbuf' value. kernel uses another value to check user supplied arguments, and this value is ~4-5% less than maxsockbuf. Therefore attempt to use 'maxsockbuf' as bufsize will fail in 100% of cases. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030304040434.A42256>