diff options
| author | Nick Mathewson <nickm@torproject.org> | 2024-02-06 11:18:31 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2024-02-06 13:00:44 -0500 |
| commit | db80b935f799ab44750ff378267b10a967af38e3 (patch) | |
| tree | 12be4d952e51f6102fee807c25532025fad91def /spec/dos-spec | |
| parent | ad73886e2a38255b5b0b599628f67fe820a5c440 (diff) | |
| download | torspec-db80b935f799ab44750ff378267b10a967af38e3.tar.gz torspec-db80b935f799ab44750ff378267b10a967af38e3.zip | |
Apply "cell" and "message" consistently
Done by grepping for "cell" and making sure it was accurate in every
place where it occurs. In tor-spec, I also searched for "message".
Part of #253.
Diffstat (limited to 'spec/dos-spec')
| -rw-r--r-- | spec/dos-spec/memory-exhaustion.md | 4 | ||||
| -rw-r--r-- | spec/dos-spec/overview.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/spec/dos-spec/memory-exhaustion.md b/spec/dos-spec/memory-exhaustion.md index 2cc55eb..14c1f6b 100644 --- a/spec/dos-spec/memory-exhaustion.md +++ b/spec/dos-spec/memory-exhaustion.md @@ -23,7 +23,7 @@ or derived from a fraction of the total amount of system RAM. As of Tor 0.4.7.x, the MaxMemInQueues mechanism tracks the following kinds of allocation: -- Cells queued on circuits. +- Relay cells queued on circuits. - Per-connection read or write buffers. - On-the-fly compression or decompression state. - Half-open stream records. @@ -59,7 +59,7 @@ oldest data. (For example, a circuit on which a single cell has been queued for 5 minutes would be freed before a circuit where 100 cells have been queued for 5 seconds.) "Data queued on a circuit" includes all data that we could drop if the circuit were destroyed: -not only the cells on the circuit's cell queue, but also any bytes +not only the cells on the circuit's relay cell queue, but also any bytes queued in buffers associated with streams or half-stream records attached to the circuit. diff --git a/spec/dos-spec/overview.md b/spec/dos-spec/overview.md index 0ea0994..81b7e35 100644 --- a/spec/dos-spec/overview.md +++ b/spec/dos-spec/overview.md @@ -32,7 +32,7 @@ Instead C Tor relies on limits for protocol resources, like circuits extensions Relay operators can place hard limits on total bandwidth using the `Bandwidth` or `RelayBandwidth` options. These options can help relay operators avoid bandwidth peaks on their network, however they aren't designed as denial of service prevention mechanisms. Beyond just shaving off harmful bandwidth peaks it's important that normal service is not disrupted too much, and especially not disrupted in a targetable way. -To approximate this goal we rely on [flow control](../tor-spec/flow-control.md) and fair dequeueing of relayed cells. +To approximate this goal we rely on [flow control](../tor-spec/flow-control.md) and fair dequeueing of relay cells. ## Protocol resources |