Where is pthread stack min

RedHat Commands. OpenSolaris Commands. Linux Commands. SunOS Commands. FreeBSD Commands. Full Man Repository. Advanced Search. Contact Us. Forum Rules. Mark Forums Read. Thread Tools. View Public Profile for dawwin. Find all posts by dawwin. View Public Profile for citaylor. Find all posts by citaylor. I have a question about the stack size of a process on Linux. Is this stack size determined at linkage time and is coded in the ELF file?

I wrote a I would like to monitor the the context switching behavior in a multi-threaded pthread application. A Naive question.. How do I determine if a detached pthread is still alive? I have a communication channel with the thread a uni-directional queue pointing outwards from I am working on Ubuntu How do I find out the maximum call stack size of a process and also the size of each frame of the stack?

The actual limit will probably be based upon per process address space limits on your specific system. It is not going to grow larger than that, unless you tell it to by adjusting it yourself before you create the thread s. Note: the example in the link is for trying to minimize stack usage, and finding a minimum which is dangerous, without a lot of testing. Sort of the opposite of what you seem to want to do, but the example may still be helpful to you.

Just approach it differently. In general, you should probably not need to raise the pthread stack size above the default. If you find you do, you probably should try understand why that is happening. It's fairly unusual. If you could explain what's actually happening in your own code, instead of a general question, other solutions might present themselves. I'm wondering if you are actually trying to reduce the per thread stack size, and just not explaining yourself clearly. If that's the case, the link might be helpful for that reason as well.

That is the pre-determined stack size for all newly created threads by default. So, to answer your question precisely, no you cannot set the max stack size of a thread using POSIX library. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

This requires very little RAM to hold the page table entries only. When your thread runs and tries to access a virtual address on the stack that doesn't have a physical page assigned to it yet, a hardware exception called a "page fault" is triggered by the MMU. The CPU core responds to the page fault exception by switching to a privileged execution mode which has its own stack and calling the page fault exception handler function inside the kernel.

The kernel allocates a page of physical RAM to that virtual memory page and returns back to the user space thread. The user space thread sees none of that work.

From its point of view, it just uses the stack as if the memory was there all along. Meanwhile, the stack automatically grows or doesn't to meet the thread's needs. The MMU is a key part of the hardware of today's computer systems. In particular, it's responsible for a lot of the "magic" in the system, so I highly recommend learning more about what the MMU does, and about virtual memory in general. Also, if your application is performance sensitive and deals with a significant amount of data, you should understand how the TLB the MMU's page table cache works and how you can restructure your data or your algorithms to maximize your TLB hit rate.

The stacksize attribute shall define the minimum stack size in bytes allocated for the created threads stack. In your example, the stack size is set to bytes which corresponds to 8MB, as returned by the command ulimit -s So that matches. So the thread stack size can be set either via the set function above, or the ulimit system property.

Sign up to join this community.