Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
Core
Tor
Commits
04b8af9d
Commit
04b8af9d
authored
8 years ago
by
Nick Mathewson
Browse files
Options
Downloads
Patches
Plain Diff
Whitespace fixes
parent
8cc528c7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/or/scheduler.c
+8
-8
8 additions, 8 deletions
src/or/scheduler.c
with
8 additions
and
8 deletions
src/or/scheduler.c
+
8
−
8
View file @
04b8af9d
...
...
@@ -35,8 +35,8 @@ static uint32_t sched_max_flush_cells = 16;
* This module implements a scheduler algorithm, to decide
* which channels should send/receive when.
*
* The earliest versions of Tor approximated a kind of round-robin system
among
* active connections, but only approximated it.
* The earliest versions of Tor approximated a kind of round-robin system
*
among
active connections, but only approximated it.
*
* Now, write scheduling works by keeping track of which channels can
* accept cells, and have cells to write. From the scheduler's perspective,
...
...
@@ -44,9 +44,9 @@ static uint32_t sched_max_flush_cells = 16;
*
* <ol>
* <li>
* Not open for writes, no cells to send
.
* <ul><li> Not much to do here, and the channel will have scheduler_state
==
* SCHED_CHAN_IDLE
* Not open for writes, no cells to send.
* <ul><li> Not much to do here, and the channel will have scheduler_state
*
==
SCHED_CHAN_IDLE
* <li> Transitions from:
* <ul>
* <li>Open for writes/has cells by simultaneously draining all circuit
...
...
@@ -63,9 +63,9 @@ static uint32_t sched_max_flush_cells = 16;
*
* <li> Open for writes, no cells to send
* <ul>
* <li>Not much here either; this will be the state an idle but open
channel
* can be expected to settle in. It will have scheduler_state
==
* SCHED_CHAN_WAITING_FOR_CELLS
* <li>Not much here either; this will be the state an idle but open
*
channel
can be expected to settle in. It will have scheduler_state
*
==
SCHED_CHAN_WAITING_FOR_CELLS
* <li> Transitions from:
* <ul>
* <li>Not open for writes/no cells by flushing some of the output
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment