netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: ilpo.jarvinen@helsinki.fi, shemminger@linux-foundation.org,
	noboru.obata.ar@hitachi.com, yoshfuji@linux-ipv6.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)
Date: Mon, 23 Jul 2007 11:40:00 -0700	[thread overview]
Message-ID: <46A4F600.90403@hp.com> (raw)
In-Reply-To: <20070713.231926.74749058.davem@davemloft.net>

David Miller wrote:
> From: Rick Jones <rick.jones2@hp.com>
> Date: Fri, 13 Jul 2007 09:55:10 -0700
> 
> 
>>Fine, but so?  I suspect the point of the patch is to provide a
>>lower cap on the accumulated backoff so data starts flowing over the
>>connection within that lower cap once the link is
>>restored/failed-over.
> 
> 
> The backoff is there for a reason.

I'm not disputing the general value of the backoff, nor about the value of an 
initial value of 60 seconds.  In terms of avoiding congestive collapse one does 
indeed want the exponential backoff.  I'm just in agreement with the person from 
Hitachi that allowing someone to tweak the backoff has a certain value.

60 seconds is already a trade-off between a pure (non capped) exponential 
backoff and capping the value.

rick

  reply	other threads:[~2007-07-23 19:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  7:15 [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2) OBATA Noboru
2007-07-12  9:37 ` David Miller
2007-07-12 13:59   ` OBATA Noboru
2007-07-12 20:24     ` David Miller
2007-07-12 21:12       ` Stephen Hemminger
2007-07-12 21:27         ` Rick Jones
2007-07-12 22:02           ` Stephen Hemminger
2007-07-12 22:27             ` Rick Jones
2007-07-24 13:30               ` OBATA Noboru
2007-07-13  4:29           ` Ilpo Järvinen
2007-07-13 16:55             ` Rick Jones
2007-07-14  6:19               ` David Miller
2007-07-23 18:40                 ` Rick Jones [this message]
     [not found]       ` <20070828.220447.01366772.noboru.obata.ar@hitachi.com>
     [not found]         ` <20070828.133057.107937654.davem@davemloft.net>
2007-08-29 12:26           ` OBATA Noboru
2007-08-29 16:16             ` Rick Jones
2007-08-30 12:24               ` OBATA Noboru
2007-08-29 18:15             ` David Miller
2007-07-12 20:51   ` Rick Jones
2007-07-24 13:35     ` OBATA Noboru

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=46A4F600.90403@hp.com \
    --to=rick.jones2@hp.com \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=netdev@vger.kernel.org \
    --cc=noboru.obata.ar@hitachi.com \
    --cc=shemminger@linux-foundation.org \
    --cc=yoshfuji@linux-ipv6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).