Searched refs:nanosecond (Results 1 – 25 of 141) sorted by relevance
123456
8 CRITERIA = "Fails if no timers have nanosecond resolution."17 Reads from /proc/timer_list to see if any reported timers have nanosecond
23 // nanosecond resolution.27 // Non-negative fractions of a second at nanosecond resolution.
36 nanosecond resolution, and (B) use more than 64 bits (assuming a 64 bit ``time_t``).57 To get nanosecond resolution, we simply define ``period`` to be ``std::nano``.76 at nanosecond resolution.80 and with nanosecond resolution).141 So we might ask: Do users "need" nanosecond precision? Is seconds not good enough?280 a nanosecond tick period; which is the only case where the names ``tv_sec``283 When we convert a nanosecond duration to seconds, ``fs_timespec_rep`` will398 * Its the representation used by chrono's ``nanosecond`` and ``second`` typedefs.447 a nanosecond tick period.452 * It has a larger range when representing any period longer than a nanosecond.[all …]
51 nanosecond{203 nanosecond{
100 nanosecond{367 nanosecond{606 nanosecond{
28 nanosecond{
102 nanosecond{385 nanosecond{
219 nanosecond{760 nanosecond{1266 nanosecond{
146 nanosecond{656 nanosecond{
219 nanosecond{779 nanosecond{1290 nanosecond{
220 nanosecond{780 nanosecond{1291 nanosecond{
259 nanosecond{887 nanosecond{1428 nanosecond{
219 nanosecond{733 nanosecond{1181 nanosecond{
220 nanosecond{842 nanosecond{1467 nanosecond{
263 nanosecond{880 nanosecond{1376 nanosecond{
219 nanosecond{790 nanosecond{1352 nanosecond{
263 nanosecond{893 nanosecond{1417 nanosecond{
44 // as a count of seconds and fractions of seconds at nanosecond98 // encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should110 // Signed fractions of a second at nanosecond resolution of the span
45 // nanosecond resolution in UTC Epoch time. It is encoded using the104 // seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),128 // Non-negative fractions of a second at nanosecond resolution. Negative
45 // nanosecond resolution in UTC Epoch time. It is encoded using the104 // seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),130 // Non-negative fractions of a second at nanosecond resolution. Negative
44 // as a count of seconds and fractions of seconds at nanosecond91 // Signed fractions of a second at nanosecond resolution of the span
46 // nanosecond resolution in UTC Epoch time. It is encoded using the106 // Non-negative fractions of a second at nanosecond resolution. Negative
365 nanosecond timeoutUnit = 'n' const380 case nanosecond:
214 u32 nanosecond; member