lkml.org 
[lkml]   [1998]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: mmap() versus read()
From
Date
Thomas Heide Clausen <voop@innocent.com> writes:

> [ SNIP again.... ]
>
> For your information: Solaris pukes in processes with more than
> about 20000 concurrently active threads (I can repeatidly on a
> Enterprise 2 with 1GB ram get it to puke on thread no. 14287).
> Haven't figured out why yet, though....but it would be cool
> if the Linux version didn't have such constraints....
>
> - --thomas
>
> (ps: anyone has a clue or similar experiences?)
>

Every thread allocates virtual memory for stack. Default stack size on
Solaris is quiet big, so if you want to fireup *really* big number of
threads, you need to adjust your default stack size. Otherwise your
virtual memory gets exhausted pretty fast.

This phenomena made me a lots of trouble with my initial experimenting
with threads. :)

Hope it helps.
--
Posted by Zlatko Calusic E-mail: <Zlatko.Calusic@CARNet.hr>
---------------------------------------------------------------------
Me know gammar. Me cood use it gud.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

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