Searched refs:nanosecond (Results 1 – 25 of 142) 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{
28 nanosecond{
102 nanosecond{385 nanosecond{
108 nanosecond{400 nanosecond{647 nanosecond{
114 nanosecond{
146 nanosecond{656 nanosecond{
232 nanosecond{884 nanosecond{1404 nanosecond{
282 nanosecond{283 dnam{"mga nanosecond"}284 one{"{0} ka nanosecond"}285 other{"{0} ka mga nanosecond"}1187 nanosecond{
235 nanosecond{901 nanosecond{1428 nanosecond{
236 nanosecond{902 nanosecond{1429 nanosecond{
282 nanosecond{983 nanosecond{1540 nanosecond{
169 nanosecond{552 nanosecond{835 nanosecond{
281 nanosecond{1034 nanosecond{1570 nanosecond{
232 nanosecond{935 nanosecond{1570 nanosecond{
227 nanosecond{804 nanosecond{1264 nanosecond{
236 nanosecond{904 nanosecond{1477 nanosecond{
273 nanosecond{1004 nanosecond{1559 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 should109 // Signed fractions of a second at nanosecond resolution of the span
45 // nanosecond resolution. The count is relative to an epoch at UTC midnight on106 // seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),133 // Non-negative fractions of a second at nanosecond resolution. Negative
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),130 // Non-negative fractions of a second at nanosecond resolution. Negative
230 u32 nanosecond; member