|
Quote: "gettimeofday() is **fast**"
You better believe it.
That statement has an interesting story all its own.
Far too long for a forum post but can probably be found somewhere in the development history of *nix or computer OSs in general.
For performance critical code paths, it is (still) common for those to be hand-coded and cycle counted - -
And then there is "gettimeofday()" -
This one is where both software implementors and cpu hardware implementors start doing crazy dances and hand-springs.
And they start considering hardware delay paths within a single clock cycle.
Where referencing an off-chip memory location or off-chip register location is: "too much overhead".
Yes, "gettimeofday() is **fast**"
|