Re: [time] add support for CLOCK_THREAD_CPUTIME_ID and CLOCK_PROCESS_CPUTIME_ID

[Ulrich Drepper]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christoph Lameter wrote:

> Then please sign off on the following patch:

Sorry, I fail to see the point.  The CPUTIME stuff will either way be
entire implemented at userlevel.  If we use TSC, we compute the
resolution from the CPU clock speed (no need to comment, I know it's not
reliable everywhere).  If we fall back on realtime, we will simply in
glibc map

   clock_getres (CLOCK_PROCESS_CPUTIME_ID, &ts)

to

   clock_getres (CLOCK_REALTIME, &ts)

The kernel knows nothing about this clock.

The comment changes are OK, of course.

If there is more to change this is in glibc.  So far I have not heard of
anybody wanting to use the clocks this way.  This is why we do not have
the fallback to realtime implemented.  If you say you need it I have no
problem adding appropriate patches.

- --
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBVQt32ijCOnn/RHQRAsWHAJ9q1Aztzf7/6TYQbu6X+DNQhFFW5wCfTP57
wbjQQe+iV/s1ODANFFYK+zs=
=JVgJ
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/