Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments

2012-08-30 Thread H.K. Jerry Chu
On Thu, Aug 30, 2012 at 9:45 AM, David Miller wrote: > From: Eric Dumazet > Date: Thu, 30 Aug 2012 06:12:30 -0700 > >> On Wed, 2012-08-29 at 10:25 -0700, H.K. Jerry Chu wrote: >> >>> But it probably matter slightly more for TCP Fast Open (the server >>> sid

Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments

2012-08-30 Thread H.K. Jerry Chu
On Thu, Aug 30, 2012 at 6:12 AM, Eric Dumazet wrote: > On Wed, 2012-08-29 at 10:25 -0700, H.K. Jerry Chu wrote: > >> But it probably matter slightly more for TCP Fast Open (the server >> side patch has >> been completed and will be posted soon, after I finish breaki

Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments

2012-08-29 Thread H.K. Jerry Chu
Eric, On Wed, Aug 29, 2012 at 1:51 AM, Eric Dumazet wrote: > On Tue, 2012-08-28 at 21:34 -0700, H.K. Jerry Chu wrote: > >> IMHO 31secs seem a little short. Why not change it to 6 as well because 63 >> secs still beats 93secs with 3sec initRTO and 5 retries. >> >>

Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments

2012-08-28 Thread H.K. Jerry Chu
On Sat, Aug 25, 2012 at 1:48 AM, Alexander Bergmann wrote: > On Fri, Aug 24, 2012 at 01:42:31PM -0400, David Miller wrote: >> Alex, this patch doesn't apply, it was completely corrupted by your email >> client. >> >> Make a fresh submission, with this fixed. But before you do, email the >> patch

Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments

2012-08-22 Thread H.K. Jerry Chu
On Wed, Aug 22, 2012 at 3:03 AM, Eric Dumazet wrote: > On Wed, 2012-08-22 at 12:00 +0200, Eric Dumazet wrote: >> On Wed, 2012-08-22 at 11:29 +0200, Alex Bergmann wrote: >> >> > Actual 6 SYN frames are sent. The initial one and 5 retries. >> > >> >> first one had a t0 + 0 delay. How can it count ??

Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments

2012-08-22 Thread H.K. Jerry Chu
On Tue, Aug 21, 2012 at 4:29 PM, Alex Bergmann wrote: > Hi David, > > I'm not 100% sure, but it looks like I found an RFC mismatch with the > current default values of the TCP implementation. > > Alex > > From 8b854a525eb45f64ad29dfab16f9d9f681e84495 Mon Sep 17 00:00:00 2001 > From: Alexander Berg