Bug 14380 - cpu time for multithreaded application
Summary: cpu time for multithreaded application
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 6.2
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-21 15:56 UTC by Need Real Name
Modified: 2008-08-01 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 15:38:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Test case for times() not receiving info from other threads (557 bytes, text/plain)
2003-04-22 00:30 UTC, Ulrich Drepper 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Need Real Name 2000-07-21 15:56:13 UTC 
The POSIX times() function only measures the system time of the master thread and does not take into account any time for the child threads.
Comment 1 Ulrich Drepper 2003-04-22 00:22:56 UTC 
This is a kernel issue, still present in the 2.5 kernels.
Comment 2 Ulrich Drepper 2003-04-22 00:30:56 UTC 
Created attachment 91222 [details]
Test case for times() not receiving info from other threads

The program prints currently something like

1050971188: clock 430949932, utime 0, stime 0
1050971189: clock 430950032, utime 0, stime 0

But the utime value should increase based on how much CPU time the two threads
get.
Comment 3 Bugzilla owner 2004-09-30 15:38:48 UTC 
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/
Note You need to log in before you can comment on or make changes to this bug.