| 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: | Jim Pirzyk (Jim....@disney.com) | |
| Date: | Jul 19, 2001 8:36:14 am | |
| List: | org.freebsd.freebsd-arch | |
On Thursday 19 July 2001 01:16 am, Terry Lambert wrote:
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.
Suggestions?
Change your code to not use so much auto variable space; if you are using this much space, you need to rethink your algorithm.
The program that is being used is by one of our developers and it is using recursion internally to do smog particle simulation over many frames (visual effects). Or systems are installed with 2GB of memory and they set there stack size to 128MB (from 64MB).
The program could write its data out to disk, but then the performance gets killed.
We also had to knock up the stack size on the linux systems that these programs are actually developed on.
- JimP
-- --- @(#) $Id: dot.signature,v 1.10 2001/05/17 23:38:49 Jim.Pirzyk Exp $ __o Jim....@disney.com ------------- pir...@freebsd.org _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*)
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message





