From: Patrick McHardy <kaber@trash.net>
To: OBATA Noboru <noboru.obata.ar@hitachi.com>
Cc: David Miller <davem@davemloft.net>,
Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable
Date: Mon, 25 Jun 2007 15:15:14 +0200 [thread overview]
Message-ID: <467FBFE2.7050605@trash.net> (raw)
In-Reply-To: <20070625.220939.132853560.noboru.obata.ar@hitachi.com>
OBATA Noboru wrote:
> From: OBATA Noboru <noboru.obata.ar@hitachi.com>
>
> 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 helpful on failover-capable network devices, such as an
> active-backup bonding device. On such devices, it is desirable
> that TCP retransmits a packet shortly after the failover, which
> is what I would like to do with this patch. Please see
> Background and Problem below for rationale in detail.
Would it make sense to do this per route?
next prev parent reply other threads:[~2007-06-25 13:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 13:09 [PATCH 2.6.22-rc5] TCP: Make TCP_RTO_MAX a variable OBATA Noboru
2007-06-25 13:15 ` Patrick McHardy [this message]
2007-06-25 14:45 ` Siim Põder
2007-06-25 16:08 ` Stephen Hemminger
2007-06-27 21:57 ` [MaybeSpam] " noboru.obata.ar
2007-06-25 16:07 ` Stephen Hemminger
2007-07-12 6:45 ` OBATA Noboru
2007-06-25 22:18 ` Ian McDonald
2007-06-25 22:28 ` Stephen Hemminger
2007-06-25 22:29 ` Rick Jones
2007-07-12 6:53 ` OBATA Noboru
2007-07-12 9:54 ` Ian McDonald
2007-07-12 6:56 ` OBATA Noboru
2007-06-28 1:00 ` YOSHIFUJI Hideaki / 吉藤英明
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=467FBFE2.7050605@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=noboru.obata.ar@hitachi.com \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.