Date: Mon, 19 Nov 2007 20:42:36 +0100 From: Roman Divacky <rdivacky@freebsd.org> To: Ulrich Spoerlein <uspoerlein@gmail.com> Cc: cvs-src@freebsd.org, Alfred Perlstein <alfred@freebsd.org> Subject: Re: cvs commit: src/sys/kern subr_param.c Message-ID: <20071119194236.GA61631@freebsd.org> In-Reply-To: <20071119184111.GB1516@roadrunner.spoerlein.net> References: <200710161040.l9GAes88010153@repoman.freebsd.org> <20071118224216.GA29048@freebsd.org> <20071119025328.GU8950@elvis.mu.org> <20071119184111.GB1516@roadrunner.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 19, 2007 at 07:41:11PM +0100, Ulrich Spoerlein wrote: > On Sun, 18.11.2007 at 18:53:28 -0800, Alfred Perlstein wrote: > > * Roman Divacky <rdivacky@FreeBSD.org> [071118 14:42] wrote: > > > On Tue, Oct 16, 2007 at 10:40:54AM +0000, Alfred Perlstein wrote: > > > > Modified files: > > > > sys/kern subr_param.c > > > > Log: > > > > Export maxswzone, maxbcache, maxtsiz, dfldsiz, maxdsiz, dflssiz, maxssiz, > > > > and sgrowsiz via sysctl. > > > > > > why is maxssiz RD_ONLY? its used only in exec_new_vmspace() for setting the default > > > stack area size and only if thats not set by sysentvec, so it's RW already just > > > not defined so. > > > > > > also... dflssiz is not used at all, and the "default stack size" is set by maxssiz > > > > If you think it can be safely changed, then go for it! > > Could this be done for maxdsiz, too? It's kinda sad you need to reboot a > FreeBSD system to work around the 512MB data size limit (in this day and > age, processes can easily hit the 512MB barrier) as I can see the maxdsiz is used only as a barrier for rlimit.. I see no harm in changing that to RW too.. I already asked kib@ if he's willing to commit this, waiting for answer...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071119194236.GA61631>