This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Question on glibc: free() API


 
> On Tuesday 03 March 2009 19:01:29 Bizhan Gholikhamseh 
> (bgholikh) wrote:
> > We are trying to understand a system performance issue with 
> our system.
> > We are capturing stack calls when a thread in application 
> is suspended 
> > and we see the following stack:
> >
> > free(...)
> > Pthreat_mutex_init(...)
> > pthread_wait_for_restart_signal(...)
> > pthread_sigsuspend(...)
> >
> > My question is: the thread which calls free() is suspended, 
> why? And 
> > under what condition it becomes runnable.
> 
> the malloc subsystem has locks in it
> -mike
>
We see the suspended thread block for a long time (10 to 100 msec), is
this acceptable, is this scheduler problem? This is impacting our system
performance. Any idea how to work aroung this?

Many thanks in advance,
Bizhan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]