[go: up one dir, main page]

|
|
Log in / Subscribe / Register

Pondering 2038

Pondering 2038

Posted Aug 15, 2013 15:46 UTC (Thu) by Cyberax (✭ supporter ✭, #52523)
In reply to: Pondering 2038 by joern
Parent article: Pondering 2038

Also, one CPU cycle is less than 1 microsecond. So if somebody wants to do precise timing then microseconds are not enough.

Nanoseconds, on the other hand, have more than enough precision for that.


to post comments

Pondering 2038

Posted Aug 16, 2013 2:32 UTC (Fri) by jimparis (guest, #38647) [Link]

> Also, one CPU cycle is less than 1 microsecond. So if somebody wants to do precise timing then microseconds are not enough.
>Nanoseconds, on the other hand, have more than enough precision for that.

One CPU cycle is also less than 1 nanosecond. How is that enough precision?

Pondering 2038

Posted Aug 16, 2013 2:35 UTC (Fri) by felixfix (subscriber, #242) [Link] (4 responses)

Any processor cycle rate of more than 1 Ghz has CPU cycles less than one nanosecond.

Pondering 2038

Posted Aug 16, 2013 10:48 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (3 responses)

Uhm. 1GHz is 1 microsecond (one billionth of a second) per cycle.

2GHz is 500nsec/cycle and so on.

Pondering 2038

Posted Aug 16, 2013 12:19 UTC (Fri) by mpr22 (subscriber, #60784) [Link]

micro = 10^-6. nano = 10^-9. pico = 10^-12. A 2GHz clock has a cycle time of 500ps.

Pondering 2038

Posted Aug 16, 2013 12:21 UTC (Fri) by intgr (subscriber, #39733) [Link] (1 responses)

You're mistaken.

1 thousandth of a second is a millisecond. (1 kHz)-1
1 millionth is a microsecond. (1 MHz)-1
1 billionth is a nanosecond. (1 GHz)-1

Pondering 2038

Posted Aug 16, 2013 12:32 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link]

You're right, of course.

Grrr... I blame too much coffee.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds