This is the mail archive of the glibc-bugs@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]

[Bug libc/12515] clock() should provide better precision


http://sourceware.org/bugzilla/show_bug.cgi?id=12515

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |SUSPENDED
         AssignedTo|siddhesh at redhat dot com  |unassigned at sourceware
                   |                            |dot org

--- Comment #9 from Siddhesh Poyarekar <siddhesh at redhat dot com> 2013-05-10 12:38:08 UTC ---
It's not as simple as I thought.  CLOCK_PROCESS_CPUTIME_ID will give a
timestamp and we will have to make our own estimate of what the amount of time
spent on the processor is.  I don't think there's a good way to get an initial
timestamp from userspace - the kernel is the best place to get us that.

I don't think there is a clean way to implement this outside of the kernel
without the kernel providing the necessary interface.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


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