This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Setting default/max thread stack size with rlimit
- From: Corey Minyard <minyard at acm dot org>
- To: Ulrich Drepper <drepper at redhat dot com>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Thu, 06 Feb 2003 16:00:13 -0600
- Subject: Re: Setting default/max thread stack size with rlimit
- References: <3E42CF3F.1060607@acm.org> <3E42D339.60802@redhat.com>
Ok, that's fine. I'm just curious now, what is the reasoning? I
couldn't find any documentation on this besides a few things in the
ChangeLog and include files, and those didn't give any reason why
rlim_cur was used instead of rlim_max for the max stack size of a
thread, they just talk about rlimit. I couldn't find anything searching
the web, either.
-Corey
Ulrich Drepper wrote:
Corey Minyard wrote:
I was looking at the code to set the max stack size using rlimit, and I
saw something a little wierd. LinuxThreads set the max stack size to
the current stack size from rlimit, which seems a little wierd.
What you call weird is not weird for others. The current behavior makes
perfect sense and it has been in use and documented for a long time. No
change.