May be this question is not strictly suited to this list, but I see lots of
people contributing from lots of different platforms.
The question regards to stack space management under different platforms, or
execution models.
Under my preferred platform ( QNX 4.25 ) stack space is allocated at
system allows to allocate a large stack for each process. Real
memory is used only as stack grows and as virtual addresses need to
have real memory pages vired to them.
There still is a physical fixed stack size limit, but it's generally
set quite high.
I don't know any system without shared memory
- Original Message -
From: Matthieu Herrb [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 3:52 AM
Subject: Re: stack size
mnicolet wrote (in a message from Tuesday 8)
May be this question is not strictly suited to this list, but I see
lots of
people
On Tue, 08 Jul 2003 10:13:06 -0300, mnicolet wrote:
Thank you.
You answered me what I was expecting: no system allows for a true or full
dynamic stack size.
If that's your interpretation, then I'm not sure what you mean by a full
dynamic stack size. All the operating systems he mentioned
, the stack would be dynamically allocated as required.
Than you again
- Original Message -
From: Tim Roberts [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 1:34 PM
Subject: Re: Re: stack size
On Tue, 08 Jul 2003 10:13:06 -0300, mnicolet wrote:
Thank you.
You
Tim Roberts wrote:
On Tue, 08 Jul 2003 10:13:06 -0300, mnicolet wrote:
So, my true question comes into scene.
The people who ported XFree86 to QNX 4.x setted the stack size hint to the
Watcom linker to 4 Mb ( yes, 4 Mb ) for the server.
I am wondering why a so high figure.
I am wondering (1
uses no memory and your process
allocates no data, just stack :)
Delving deeply into pedantics, the default stack size for a Win32 CreateThread
call is 1MB, but you bump into other limits long before you get to 2048 threads
(given the 2GB user-mode address space).
--
- Tim Roberts, [EMAIL
