Is time-caching necessary in tor_gettimeofday_cached_monotonic?

Could we instead replace it with reasonably fast time, where reasonably fast is OS-dependent? Or just with tor_gettimeofday()?

changed milestone to %Tor: 0.2.9.x-final

added 029-nickm-unsure actualpoints::0 component::core tor/tor milestone::Tor: 0.2.9.x-final points::1 priority::high resolution::fixed severity::normal status::closed type::defect labels

Trac:
Points: N/A to small

Marking these tickets as the ones I think I need more feedback about in order to figure out if I think it should go in 0.2.9.

Trac:
Keywords: N/A deleted, 029-nickm-unsure added

Poor performance of non-VDSO time means that we're likely to be able to do this only on some systems OR do it only for cases where higher-accuracy time is worth paying for.

Calling these "yes for 0.2.9" since a good implementation of mike's padding patches requires them.

Trac:
Keywords: 029-proposed deleted, N/A added
Milestone: N/A to Tor: 0.2.9.x-final

Trac:
Points: small to 1
Priority: Medium to High

tor_gettimeofday_cached_monotonic is dead; see #18908 (moved).

Trac:
Actualpoints: N/A to 0
Resolution: N/A to fixed
Status: new to closed

closed

changed time estimate to 8h

moved to tpo/core/tor#18909 (closed)