:Currently, the threads library only creates one guard page
:at the top (or bottom depending on how you look at it) of
:each threads stack (for stacks of default size). Thread
:stacks are allocated in sequential zones, so they are always
:placed on top of the previous threads stack, and thus already
:have a guard page below the stack.
:
:Correct me if I'm wrong, but using MAP_STACK|MAP_GUARDED
:would allocate one additional guard page for each threads
:stack.
:
:DanE.
Correct. At the moment MAP_GUARDED is a 'generic' guarding flag
and makes no assumptions about the areas being adjoining. It doesn't
cost us anything.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
- tentitive complete patch for MAP_GUARDED available Matthew Dillon
- Re: tentitive complete patch for MAP_GUARDED available Alan Cox
- Re: tentitive complete patch for MAP_GUARDED avail... Matthew Dillon
- Re: tentitive complete patch for MAP_GUARDED a... Jason Evans
- Re: tentitive complete patch for MAP_GUARD... Matthew Dillon
- Re: tentitive complete patch for MAP_GUARDED avail... Matthew Dillon
- Re: tentitive complete patch for MAP_GUARDED a... Matthew Dillon
- Re: tentitive complete patch for MAP_GUARDED available Daniel Eischen
- Re: tentitive complete patch for MAP_GUARDED avail... Matthew Dillon
- Re: tentitive complete patch for MAP_GUARDED a... Daniel Eischen
- Re: tentitive complete patch for MAP_GUARD... Matthew Dillon
- Re: tentitive complete patch for MAP_GUARDED a... Matthew Dillon
- Re: tentitive complete patch for MAP_GUARD... Matthew Dillon
