Re[2]: [Gc] Per-thread stack requirements for GC?

Ivan Maidanski ivmai at mail.ru
Thu Jun 18 08:36:11 PDT 2009


Hi!

"Talbot, George" <Gtalbot at locuspharma.com> wrote:
> I could do that, as I have debug code that can trigger a collection.  Stupid question:  how do I check the committed stack size on Linux x86_64?

I don't know. May be, look into "/proc".

BTW. What are the reasons for shrinking uncommitted stack size on a 64-bit system? (If a page is uncommitted then it doesn't occupy RAM).

> 
> --
> George T. Talbot
> <gtalbot at locuspharma.com>
> 
> 
> > -----Original Message-----
> > From: gc-bounces at napali.hpl.hp.com [mailto:gc-bounces at napali.hpl.hp.com]
> > On Behalf Of Ivan Maidanski
> > Sent: Thursday, June 18, 2009 11:04 AM
> > To: gc at napali.hpl.hp.com
> > Subject: Re: [Gc] Per-thread stack requirements for GC?
> >
> > Hi!
> >
> > "Talbot, George" <Gtalbot at locuspharma.com> wrote:
> > > Hey guys,
> > >
> > > Technical question-I have a program using the GC with many threads, and
> > am trying to reduce my memory consumption by reducing the thread stack
> > size from 2MB on my Linux machine to something smaller.
> >
> > 2MB is the size of uncommitted stack, right?
> >
> > You're trying to shrink that size because your app is near the virtual
> > memory limit, right?
> >
> > >
> > > Does anybody have a handle on the stack-size requirements of the BDW
> > collector so that I can safely size my thread stacks?
> >
> > Check the committed stack size (for a non-main thread) after GC_gcollect().
> >
> > >
> > > Thanks.
> > >
> > > --
> > > George T. Talbot
> > > <gtalbot at locuspharma.com>
> >
Bye.


More information about the Gc mailing list