Hi,
On Tue, Dec 18, 2007 at 03:39:17AM +, Peter Wemm wrote:
> peter 2007-12-18 03:39:17 UTC
>
> FreeBSD src repository
>
> Modified files:(Branch: RELENG_6)
> sys/netinet tcp_subr.c tcp_timer.h
> Log:
> MFC: scale TCPTV_MIN with hz, not a fixed number of t
On 31 Jul, Peter Wemm wrote:
> peter 2007-07-31 22:11:56 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/netinet tcp_subr.c tcp_timer.h
> Log:
> Change TCPTV_MIN to be independent of HZ. While it was documented to
> be in ticks "for algorithm stability" whe
On Wed, Aug 01, 2007 at 06:38:01PM +1000, Peter Jeremy wrote:
> My gut feeling is that putting an artifical lower bound on the RTT is
> a hackish way to control the retransmit timeout - I thought the TCP
> algorithms relied on knowing the real RTT to correctly handle
> retransmissions. A variable
At 10:11 PM + 7/31/07, Peter Wemm wrote:
The old behavior (with hz=100) caused the connection to typically
drop between 90 and 110 seconds of getting no response.
Now boot with kern.hz=1000 (default). The same test causes the
ssh session to drop after just 9-10 seconds. This is a
On 2007-Jul-31 22:11:56 +, Peter Wemm <[EMAIL PROTECTED]> wrote:
> To demonstrate, boot with kern.hz=100. ssh to a box on local ethernet
> and establish a reliable round-trip-time (ie: type a few commands).
> Then unplug the ethernet and press a key. Time how long it takes to
> drop the c
