| From | Sent On | Attachments |
|---|---|---|
| Jim Pirzyk | Jul 18, 2001 4:18 pm | |
| Terry Lambert | Jul 19, 2001 1:15 am | |
| Jim Pirzyk | Jul 19, 2001 8:36 am | |
| Bakul Shah | Jul 19, 2001 9:01 am | |
| Jim Pirzyk | Jul 19, 2001 9:07 am | |
| Terry Lambert | Jul 20, 2001 8:40 am | |
| Terry Lambert | Jul 20, 2001 8:44 am | |
| Bakul Shah | Jul 20, 2001 10:08 am | |
| Jim Pirzyk | Jul 20, 2001 12:03 pm | |
| Jim Pirzyk | Jul 20, 2001 12:55 pm | |
| Bruce Evans | Jul 21, 2001 4:40 am |
| Subject: | Re: Setting the default MAX Stack size | |
|---|---|---|
| From: | Bruce Evans (bd...@zeta.org.au) | |
| Date: | Jul 21, 2001 4:40:15 am | |
| List: | org.freebsd.freebsd-arch | |
On Wed, 18 Jul 2001, Jim Pirzyk wrote:
So I have a need to increase the max stack size in the kernel. There currently is no knob to do this. I though of implementing it like the max data size knob (MAXDSIZ). Is this the best answer or should it maybe be done via read only sysctl (and then can be set in the /boot/loader.conf)? I know how to do the former, but I am not sure about the latter.
This (set MAXSSIZ in the same way as MAXDSIZ) is the best answer. There is no point in making it more tunable than MAXDSIZ.
Notes: - MAXSSIZ used to be an option, just like MAXDSIZ. There are ifdefs for both in <machine/vmparam.h>. This was broken by not putting MAXSSIZ in sys/conf/options. - the stack size should normally be limited using login.conf or the stack size rlimit. These don't apply here because MAXSSIZ gives the maximum that can be set using these.
Bruce
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message





