summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-14 17:48:45 -0400
committerNick Mathewson <nickm@torproject.org>2011-03-14 17:48:45 -0400
commit1d36a8e9ae766f67097f4c5e522c33ff0c4a693f (patch)
tree51e218c8c2ca7077b49032dc4a3e48d44430c861 /changes
parentb97d9abd0940037b249a1ee56724dbfed904263b (diff)
downloadtor-1d36a8e9ae766f67097f4c5e522c33ff0c4a693f.tar.gz
tor-1d36a8e9ae766f67097f4c5e522c33ff0c4a693f.zip
Consider sending stream-level SENDME cells on partial flushes.
Right now, we only consider sending stream-level SENDME cells when we have completely flushed a connection_edge's outbuf, or when it sends us a DATA cell. Neither of these is ideal for throughput. This patch changes the behavior so we now call connection_edge_consider_sending_sendme when we flush _some_ data from an edge outbuf. Fix for bug 2756; bugfix on svn r152.
Diffstat (limited to 'changes')
-rw-r--r--changes/bug275611
1 files changed, 11 insertions, 0 deletions
diff --git a/changes/bug2756 b/changes/bug2756
new file mode 100644
index 0000000000..0cad515a1b
--- /dev/null
+++ b/changes/bug2756
@@ -0,0 +1,11 @@
+ o Minor bugfixes (spec conformance, performance):
+ - We now ask the other side of a stream (the client or the exit)
+ for more data on that stream when the amount of queued data on
+ that stream dips low enough. Previously, we wouldn't ask the
+ other side for more data until either it sent us more data
+ (which it wasn't supposed to do if it had exhausted its
+ window!) or until we had completely flushed all our queued
+ data. Fixing this should improve throughput. Fixes bug 2756;
+ bugfix on the earliest released versions of Tor (svn commit
+ r152).
+