aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-26 01:34:42 -0400
committerNick Mathewson <nickm@torproject.org>2011-03-30 14:41:41 -0400
commitaa950e6c48471f00ff9497fa4e9fad1c71e75868 (patch)
tree58a1a24fafb531c7f4214cba8a1bf98041fe6ae6 /changes
parent5eaba5ac2128eebf095441e23b6b7516ce35dd5d (diff)
downloadtor-aa950e6c48471f00ff9497fa4e9fad1c71e75868.tar
tor-aa950e6c48471f00ff9497fa4e9fad1c71e75868.tar.gz
Use timevals, not time_t, when expiring circuits.
We've got millisecond timers now, we might as well use them. This change won't actually make circuits get expiered with microsecond precision, since we only call the expiry functions once per second. Still, it should avoid the situation where we have a circuit get expired too early because of rounding. A couple of the expiry functions now call tor_gettimeofday: this should be cheap since we're only doing it once per second. If it gets to be called more often, though, we should onsider having the current time be an argument again.
Diffstat (limited to 'changes')
-rw-r--r--changes/cbt_hi_res7
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/cbt_hi_res b/changes/cbt_hi_res
new file mode 100644
index 000000000..c0df1183c
--- /dev/null
+++ b/changes/cbt_hi_res
@@ -0,0 +1,7 @@
+ o Minor features
+ - When expiring circuits, use microsecond timers rather than one-second
+ timers. This can avoid an unpleasant situation where a circuit is
+ launched near the end of one second and expired right near the
+ beginning of the next, and prevent fluctuations in circuit timeout
+ values.
+