Hi, Stephen.
Thank you for your comments. I will fix them and re-send the
patch for 2.6.22.
From: Stephen Hemminger [EMAIL PROTECTED]
Subject: Re: [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable
Date: Mon, 25 Jun 2007 09:07:48 -0700
diff -uprN -X a/Documentation/dontdiff
linux-2.6.22
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 PROTECTED]
Make TCP_RTO_MAX a variable, and allow
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]
Make TCP_RTO_MAX a variable, and allow a user
On 7/12/07, OBATA Noboru [EMAIL PROTECTED] wrote:
Ian McDonald wrote:
On 6/26/07, OBATA Noboru [EMAIL PROTECTED] wrote:
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
Patrick McHardy wrote:
OBATA Noboru wrote:
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
In article [EMAIL PROTECTED] (at Mon, 25 Jun 2007 22:09:39 +0900 (JST)),
OBATA Noboru [EMAIL PROTECTED] says:
Please note that this is effective in IPv6 as well.
Of course, I'm happy with this.
--yoshfuji
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a
OBATA Noboru wrote:
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
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
quite
On Mon, 25 Jun 2007 22:09:39 +0900 (JST)
OBATA Noboru [EMAIL PROTECTED] wrote:
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
On Mon, 25 Jun 2007 15:15:14 +0200
Patrick McHardy [EMAIL PROTECTED] wrote:
OBATA Noboru wrote:
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
Ian McDonald wrote:
On 6/26/07, OBATA Noboru [EMAIL PROTECTED] wrote:
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,
Yo!
Patrick McHardy wrote:
OBATA Noboru wrote:
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.
12 matches
Mail list logo