Date: Wed, 27 Jan 1999 16:28:14 -0600 From: "Richard Seaman, Jr." <dick@tar.com> To: Luke <lh@aus.org> Cc: current@FreeBSD.ORG Subject: Whats VM_STACK (was Re: Netscape | Mozilla) Message-ID: <19990127162814.O421@tar.com> In-Reply-To: <199901271716.MAA20727@ayukawa.aus.org>; from Luke on Wed, Jan 27, 1999 at 12:35:09PM -0500 References: <XFMail.990127180059.asmodai@wxs.nl> <199901271716.MAA20727@ayukawa.aus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 27, 1999 at 12:35:09PM -0500, Luke wrote: > what is this VM_STACK option? Its some new code to manage "autogrow" stacks. The existing (old) code made a process stack autogrow. But, its useful to be able to create additional autogrow memory regions to use as thread stacks in threaded programs. The additional code does this, and uses the same code to manage the process stack. Its been around for a month or so, hidden behind the VM_STACK option (ie. you had to add -DVM_STACK when compiling kernel/world). The idea was that if it works, the option would be removed and the code made permanent. For i386 machines, the "option" was made the default about 2 days ago for -current, and was made the default for 3.X today. You can still pull it out if you have problems, as its still mostly hidden behind the VM_STACK defines. -DVM_STACK is now just turned on by default. As soon as it gets more testing on alpha machines, and if it seems to continue to work elsewhere, and if there's no great objection, its likely to become permanent. mmap(2) has some more information (if your sources are very current). -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990127162814.O421>