diff options
author | Matt Traudt <sirmatt@ksu.edu> | 2017-09-12 22:12:24 -0400 |
---|---|---|
committer | David Goulet <dgoulet@torproject.org> | 2017-09-15 11:40:59 -0400 |
commit | 61fc9c41ad8241be06587f28d1542c0caba55d1b (patch) | |
tree | 6849cada35055b1c5da9300389168efc38cebf50 /src/or/scheduler.h | |
parent | 6e598bbcd8ee5b0dfec8f6713679988294cb2523 (diff) | |
download | tor-61fc9c41ad8241be06587f28d1542c0caba55d1b.tar.gz tor-61fc9c41ad8241be06587f28d1542c0caba55d1b.zip |
sched: switch to monotonic time; add/fix comments, style, and logs msgs
Diffstat (limited to 'src/or/scheduler.h')
-rw-r--r-- | src/or/scheduler.h | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/or/scheduler.h b/src/or/scheduler.h index ce5163b817..6cf75c585a 100644 --- a/src/or/scheduler.h +++ b/src/or/scheduler.h @@ -62,10 +62,10 @@ typedef struct scheduler_s { /* (Optional) To be called whenever Tor finds out about a new consensus. * First the scheduling system as a whole will react to the new consensus - * and change the scheduler if needed. After that, whatever is the (possibly - * new) scheduler will call this so it has the chance to react to the new - * consensus too. If there's a consensus parameter that your scheduler wants - * to keep an eye on, this is where you should check for it. */ + * and change the scheduler if needed. After that, the current scheduler + * (which might be new) will call this so it has the chance to react to the + * new consensus too. If there's a consensus parameter that your scheduler + * wants to keep an eye on, this is where you should check for it. */ void (*on_new_consensus)(const networkstatus_t *old_c, const networkstatus_t *new_c); |