[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[nptl] Re: NPTL Issue getrusage() / times
Moin ;)
> accordingly to SUSv3, getrusage() and times() should return the timing
> (user and system time) information for the *process*. That is the sum
> over all thread's time.
>
> With NPTL, the timing is thread-wise only. That is, the timing is given
> only for the thread that calls getrusage(), resp. times(). This deviates
> from SUSv3.
>
> I would definitively keep that neat feature of obtaining timing
> thread-wise, but not with the standard getrusage(), resp. times().
>
> If you like, I can devise a test program proving my claim.
>
I don't know the getrusage() and times() internals, but it looks like
things are moving in the glibc as the clocks CLOCK_*_CPUTIME_ID are
bogus in the current CVS (are you subscribed to libc-alpha
mailing-list?). Maybe this is related to the issue you're seeing?
Seb.
-------------------------------
Sebastien DECUGIS
NPTL Test & Trace Project
http://nptl.bullopensource.org/
"You may fail if you try.
You -will- fail if you don't."
Liste de diffusion nptl
Pour se désinscrire : mailto:nptl_request@bullopensource.org?subject=unsubscribe