[lkml]   [2002]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Q: behaviour of mlockall(MCL_FUTURE) and VM_GROWSDOWN segments
Andrew Morton <> writes:

> So in this case, the behaviour I would prefer is MCL_FUTURE for
> all vma's *except* the stack. Stack pages should be locked
> only when they are faulted in. Hard call.

There is just one problem: linuxthread stacks are just ordinary mappings
and they are in no way special to the kernel; they aren't VM_GROWSDOWN.
You would need to add a way to the kernel first to tag the linux thread
stacks in a way that is recognizable to mlockall and then do that
from linuxthreads.

I think for the normal stack - real VM_GROWSDOWN segments - mlockall
already does the right thing.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:15    [W:0.066 / U:0.772 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site