summaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorteor <teor2345@gmail.com>2017-07-05 01:45:28 +1000
committerNick Mathewson <nickm@torproject.org>2017-07-07 13:18:04 -0400
commit527c0735f11d5a36aa1fb84dc30b624139ba8406 (patch)
tree694fb93a53d4e791b135b9821669af1bc8b26709 /src/or/or.h
parent32f0cbc0f6fc7a53fc88a144e42fea9aca2cd073 (diff)
downloadtor-527c0735f11d5a36aa1fb84dc30b624139ba8406.tar.gz
tor-527c0735f11d5a36aa1fb84dc30b624139ba8406.zip
Comment that failure schedules always use exponential backoff
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/or/or.h b/src/or/or.h
index b7c67baf93..8a217a079e 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -1981,7 +1981,9 @@ typedef struct download_status_t {
* or after each failure? */
download_schedule_backoff_bitfield_t backoff : 1; /**< do we use the
* deterministic schedule, or random
- * exponential backoffs? */
+ * exponential backoffs?
+ * Increment on failure schedules
+ * always use exponential backoff. */
uint8_t last_backoff_position; /**< number of attempts/failures, depending
* on increment_on, when we last recalculated
* the delay. Only updated if backoff