Skip to contentSkip to conversation

document CLOCK_MONOTONIC_COARSE

PATCH In review Andy Isaacson 2 participants 4 messages May 31, 2012 – Jun 4, 2012 3 messages not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore

Andy Isaacson

author
#0 lore raw

PATCH 1/1 document CLOCK_MONOTONIC_COARSE

Let's try that again without using gmail.

-andy

commit 782f8fd7a4ecd601d46e13e6a55a04662bae2f27

Author: Andy Isaacson <adi-psgPW5cihnJWk0Htik3J/[email protected]>
Date:   Thu May 31 16:36:30 2012 -0700

clock_getres.2: document CLOCK_MONOTONIC_COARSE

man2/clock_getres.2 +7 -0
index 67713c7..01289d6 100644
@@ -136,6 +136,13 @@ Similar to
 but provides access to a raw hardware-based time
 that is not subject to NTP adjustments.
 .TP
+.BR CLOCK_MONOTONIC_COARSE " (since Linux 2.6.32; Linux-specific)"
+.\" Added in commit da15cfdae03351c689736f8d142618592e3cebc3, John Stultz, Aug 19 2009
+Similar to
+.BR CLOCK_MONOTONIC ,
+but provides only the time at the most recent clock tick.  This can be
+faster to access.
+.TP
 .B CLOCK_PROCESS_CPUTIME_ID
 High-resolution per-process timer from the CPU.
 .TP

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 20120531235955.GA18876-psgPW5cihnJWk0Htik3J/[email protected]

#2 lore raw
Quoted 2 lines · Andy Isaacson

+.BR CLOCK_MONOTONIC_COARSE " (since Linux 2.6.32; Linux-specific)"
+.\" Added in commit da15cfdae03351c689736f8d142618592e3cebc3, John Stultz, Aug 19 2009

Is it necessary to specify the commit rev?

Signature · 5 lines
Alexandre Bique
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): CAP737o+rUezC4tiCra-qTiVL2XxbKJ7Z+9oeHrw6hCEkEX8Cyg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

author
#4 lore raw
Quoted 5 lines · Alexandre Bique
Quoted 2 lines · Andy Isaacson

+.BR CLOCK_MONOTONIC_COARSE " (since Linux 2.6.32; Linux-specific)"
+.\" Added in commit da15cfdae03351c689736f8d142618592e3cebc3, John Stultz, Aug 19 2009

Is it necessary to specify the commit rev?

Speaking as a git user, it's much more helpful to provide the commitID than to just provide committer+date as was done for other items in this file. It allows "git tag --contains da15cfdae" to find out what release it was merged in, for example.

Is there any downside to having the commit hash in the comment?

-andy
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): CAE_FxDi3ecT8vJnJdeh_T1_2TaTdAWBn=iSb_Z_-EVMW9+6Wxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

#6 lore raw
Quoted 6 lines · Andy Isaacson
Quoted 4 lines · Alexandre Bique
Quoted 2 lines · Andy Isaacson

+.BR CLOCK_MONOTONIC_COARSE " (since Linux 2.6.32; Linux-specific)"
+.\" Added in commit da15cfdae03351c689736f8d142618592e3cebc3, John Stultz, Aug 19 2009

Quoted 8 lines
Quoted 1 line

Is it necessary to specify the commit rev?

Speaking as a git user, it's much more helpful to provide the commitID than to just provide committer+date as was done for other items in this file.  It allows "git tag --contains da15cfdae" to find out what release it was merged in, for example.

Is there any downside to having the commit hash in the comment?

I agree with you, it is convenient to have the commit revision when you need to dig into Linux source code.

Signature · 5 lines
Alexandre Bique
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html