Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

2007-08-30 Thread OBATA Noboru
Hi Rick, From: Rick Jones <[EMAIL PROTECTED]> Subject: Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2) Date: Wed, 29 Aug 2007 09:16:43 -0700 > OBATA Noboru wrote: > > What about another option to let TCP have a notification? > > > > Can it be a sol

Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

2007-08-29 Thread OBATA Noboru
From: David Miller <[EMAIL PROTECTED]> Subject: Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2) Date: Tue, 28 Aug 2007 13:30:57 -0700 (PDT) > From: OBATA Noboru <[EMAIL PROTECTED]> > Date: Tue, 28 Aug 2007 22:04:47 +0900 (JST) > > > (1) Make the applicati

Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

2007-08-28 Thread OBATA Noboru
Hi Dave, From: David Miller <[EMAIL PROTECTED]> Subject: Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2) Date: Thu, 12 Jul 2007 13:24:48 -0700 (PDT) > From: OBATA Noboru <[EMAIL PROTECTED]> > Date: Thu, 12 Jul 2007 22:59:50 +0900 (JST) > > > How do you

Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

2007-07-24 Thread OBATA Noboru
devices as well is desired. * If the failure and recovery are not visible locally, TCP notifications do not help. Regards, -- OBATA Noboru ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

2007-07-24 Thread OBATA Noboru
values and retry counts of probe packets are suitable for detecting failure of a certain combination of network equipments. (e.g., 5sec timeout, retries 4 times) Shorter is better. And application timeout (or system timeout) is given as an end-user requirement. There is little change of negot

Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

2007-07-12 Thread OBATA Noboru
EMAIL PROTECTED] > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], >netdev@vger.kernel.org > Date: Thu, 12 Jul 2007 02:37:10 -0700 (PDT) > X-Mailer: Mew version 5.1.52 on Emacs 21.4 / Mule 5.0 (SAKAKI) > > From: OBATA Noboru <[EMAIL PROTECTED]> > Date: Thu, 12 Jul 20

[PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

2007-07-12 Thread OBATA Noboru
Hi David, Patch (take 2) for making TCP_RTO_MAX a variable. Suggestions from Stephen for the first version are merged. Any comments are appreciated. From: OBATA Noboru <[EMAIL PROTECTED]> Make TCP_RTO_MAX a variable, and allow a user to change it via a new sysctl entry /proc/sys/ne

Re: [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable

2007-07-11 Thread OBATA Noboru
From: "Ian McDonald" <[EMAIL PROTECTED]> Subject: [MaybeSpam] Re: [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable Date: Tue, 26 Jun 2007 10:18:46 +1200 > On 6/26/07, OBATA Noboru <[EMAIL PROTECTED]> wrote: > > From: OBATA Noboru <[EMAIL PROTECTED]> >

Re: [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable

2007-07-11 Thread OBATA Noboru
From: Rick Jones <[EMAIL PROTECTED]> Subject: Re: [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable Date: Mon, 25 Jun 2007 15:29:26 -0700 > Ian McDonald wrote: > > On 6/26/07, OBATA Noboru <[EMAIL PROTECTED]> wrote: > > > >> From: OBATA Noboru <[EMAIL P

Re: [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable

2007-07-11 Thread OBATA Noboru
> + .procname = "tcp_rto_max", > > + .data = &sysctl_tcp_rto_max, > > + .maxlen = sizeof(int), > > + .mode = 0644, > > + .proc_handler = &proc_tcp_rto_max, > > +

[PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable

2007-06-25 Thread OBATA Noboru
From: OBATA Noboru <[EMAIL PROTECTED]> Make TCP_RTO_MAX a variable, and allow a user to change it via a new sysctl entry /proc/sys/net/ipv4/tcp_rto_max. A user can then guarantee TCP retransmission to be more controllable, say, at least once per 10 seconds, by setting it to 10. This is