aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2003-11-10 23:10:42 +0000
committerRoger Dingledine <arma@torproject.org>2003-11-10 23:10:42 +0000
commit1c37f631ff28e82720aec3c0f083b326dc0e38c8 (patch)
treed0d563b2ecc880f0e092e02ec4ac0aba80b941d0
parent1969c8a92f628d6c4dcbd8e179d6a3e8f59bd6e3 (diff)
downloadtor-1c37f631ff28e82720aec3c0f083b326dc0e38c8.tar.gz
tor-1c37f631ff28e82720aec3c0f083b326dc0e38c8.zip
add a paragraph that should have been there
svn:r781
-rw-r--r--doc/tor-design.tex7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/tor-design.tex b/doc/tor-design.tex
index bc3f88f3c1..bd2ef4af9f 100644
--- a/doc/tor-design.tex
+++ b/doc/tor-design.tex
@@ -936,7 +936,7 @@ reaches 0, it stops reading from streams destined for that OR.
\textbf{Stream-level throttling}:
The stream-level congestion control mechanism is similar to the
-circuit-level mechanism above. ORs and OPs use \emph{relay sendme} cells
+circuit-level mechanism. ORs and OPs use \emph{relay sendme} cells
to implement end-to-end flow control for individual streams across
circuits. Each stream begins with a packaging window (currently 500 cells),
and increments the window by a fixed value (50) upon receiving a \emph{relay
@@ -950,6 +950,11 @@ Currently, non-data relay cells do not affect the windows. Thus we
avoid potential deadlock issues, for example, arising because a stream
can't send a \emph{relay sendme} cell when its packaging window is empty.
+These arbitrarily chosen parameters
+%are probably not optimal; more
+%research remains to find which parameters
+seem to give tolerable throughput and delay; more research remains.
+
\Section{Other design decisions}
\SubSection{Resource management and denial-of-service}