[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: constrained socket buffers patch

To: or-talk@xxxxxxxxxxxxx
Subject: Re: constrained socket buffers patch
From: coderman <coderman@xxxxxxxxx>
Date: Fri, 13 Jul 2007 02:59:36 -0700
Cc: or-dev@xxxxxxxxxxxxx
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Fri, 13 Jul 2007 05:59:46 -0400
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UZkKy9ltjrHynUwnPrMfgTn45Qyaeb6SnuDpvUXVNDwlo6EOkZ/2/Kiwf7dJmoTBjq8vA8B2sHo1UeCaquxPzkt/ojOrR0iafpK5JyByO7vrbSivIGcH69TLZu1eOYdbZT7G/a8NDXgyijZ9r4oe10kaKU6mvtKgQBfsGci+sWs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=k1p6o9MzwNCAkduCCg7BCo9H+yjPdVbSqVZvvOB3rx77/u0DE/eBAZYUfJkf7/lXH7BMOXy3UC7fL0lmhLR/A+udbXMX6z2IxTw5Bo37x3GAGqrvnv76N+ScqozHueJziWh71n19wUTeKiVzZ9pVP4jCpK3/D35i9uu4TR5NXnI=
In-reply-to: <7i4pk8ptak.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
References: <4ef5fec60707111454v5eea2f35iee3bb7b6d2a747a0@xxxxxxxxxxxxxx> <7iwsx5oz5a.fsf@xxxxxxxxxxxxxxxxxxxxxxx> <20070713070845.GJ11269@xxxxxxxxxxxxxx> <7i4pk8ptak.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

On 7/13/07, Juliusz Chroboczek <Juliusz.Chroboczek@xxxxxxxxxxxxxx> wrote:

...
There is another issue, which doesn't appear in the above.  TCP is
extremely sensitive to packet loss when the window is smaller than
4 packets (fast retransmit doesn't work in that case).  So could
I suggest a default value for ConstrainedSockSize of 8 kB?


this is a good idea.  16k might be even better if it worked reliably
(the usual default is 32 to 64k).

i've updated the patch to provide better documentation on this option
in the man page and set the default to 8k per your suggestion.[0]

one last note: this should work on win32 sockets and may help reduce
the windows buffer problem. [1]

any feedback testing this patch on vservers or win32 is appreciated.

best regards,


0. updated constrained socket buffers patches:
 http://peertech.org/pub/tor-constrained-sockets-0.1.2.14.patch
 md5:ff2432af49e3348e12de61a795b10840
 sha1:8a18a8a1b2dc872fff03d7611773f615b3382d28
 ---
 http://peertech.org/pub/tor-constrained-sockets-0.2.0.2-alpha.patch
 md5:b53e37863612110e764769b84f527609
 sha1:7e990582ea0a240bd54b3ba7ea97ede72a592856

1. "Windows Buffer Problems (WSAENOBUFS)"
 http://wiki.noreply.org/noreply/TheOnionRouter/WindowsBufferProblems

Follow-Ups:
- Re: constrained socket buffers patch
  - From: coderman
- Re: constrained socket buffers patch
  - From: Juliusz Chroboczek

References:
- constrained socket buffers patch
  - From: coderman
- Re: constrained socket buffers patch
  - From: Juliusz Chroboczek
- Re: constrained socket buffers patch
  - From: Roger Dingledine
- Re: constrained socket buffers patch
  - From: Juliusz Chroboczek

Prev by Author: constrained socket buffers patch
Next by Author: Re: constrained socket buffers patch
Previous by thread: Re: constrained socket buffers patch
Next by thread: Re: constrained socket buffers patch
Index(es):
- Author
- Thread