[concurrency-interest] Thread Stack Size and Thread Local Data
ramesh.mandaleeka at gmail.com
Tue Mar 23 19:28:20 EDT 2010
Thank you all for the response.
David - I was referring to the data that we store in Thread Local variables.
I guess it goes on to the threads stack, right?
On Tue, Mar 23, 2010 at 6:32 PM, David Holmes <davidcholmes at aapt.net.au>wrote:
> Hi Ramesh,
> The default Java thread stack size is platform specific but can be set with
> -Xss parameter on JVM startup (or can be set for individual threads via
> their constructor). This stack size is not related to that seen in ulimit
> because the VM explicitly sets the stack size when native threads are
> As for "Thread Local Data" I'm not sure exactly what you mean by that.
> David Holmes
> -----Original Message-----
> *From:* concurrency-interest-bounces at cs.oswego.edu [mailto:
> concurrency-interest-bounces at cs.oswego.edu]*On Behalf Of *Ramesh
> *Sent:* Wednesday, 24 March 2010 2:53 AM
> *To:* concurrency-interest at cs.oswego.edu
> *Subject:* [concurrency-interest] Thread Stack Size and Thread Local Data
> May be not directly related to concurrency. But here is my question:
> What is the default size of the Thread Stack and Thead Local Data. Does it
> depend on OS? When I did ulimit command on my server I see stack size. Does
> this related to Thread Stack in Java.
> *ulimit -a
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 532480
> max locked memory (kbytes, -l) 32
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> *stack size (kbytes, -s) 10240*
> cpu time (seconds, -t) unlimited
> max user processes (-u) 532480
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest