According to documentations I found, it seems to be used for "context switching". However, I find it hard to estimate how much working space is actually needed. I find it intriguing to dig through the code because I couldn't find a straightforward way to search for relevant code. I boil down my questions into these:
- Does each OS call use some?
- Does context switching change the stack pointer address?
- Is it only the system calls that consumes working space? Or does local variables to a thread also use said thread stack?
What is the thread working area actually used for?
- Giovanni
- Site Admin
- Posts: 14457
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
Re: What is the thread working area actually used for?
The working area is the thread stack area, anything using stack requires space there.
Giovanni
Giovanni
Who is online
Users browsing this forum: No registered users and 14 guests