From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: hancockr@shaw.ca, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
stephen.hemminger@vyatta.com, romieu@fr.zoreil.com,
shemminger@vyatta.com, dusanc@gmail.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: [Bridge] [RFC] bridge: STP timer management range checking
Date: Tue, 02 Sep 2008 17:00:40 -0700 [thread overview]
Message-ID: <48BDD3A8.6070500@hp.com> (raw)
In-Reply-To: <20080902.164130.156055373.davem@davemloft.net>
David Miller wrote:
> From: Rick Jones <rick.jones2@hp.com>
> Date: Tue, 02 Sep 2008 09:40:46 -0700
>>Can one change the TCP maximum RTO to be smaller than specified in the specs?
> We always min-clamp the RTO at RTO calculation time in order to be
> compatible with BSD's coarse grained times.
But tuning TCP_RTO_MAX isn't permitted right? I'm drawing (perhaps
flawed) parallels/distinctions between what is/isn't permitted to tweak
for timers for one protocol versus another and wondering which may be a
case of sauce for the goose/gander.
rick jones
WARNING: multiple messages have this Message-ID (diff)
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: alan@lxorguk.ukuu.org.uk, stephen.hemminger@vyatta.com,
shemminger@vyatta.com, dusanc@gmail.com, romieu@fr.zoreil.com,
hancockr@shaw.ca, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [RFC] bridge: STP timer management range checking
Date: Tue, 02 Sep 2008 17:00:40 -0700 [thread overview]
Message-ID: <48BDD3A8.6070500@hp.com> (raw)
In-Reply-To: <20080902.164130.156055373.davem@davemloft.net>
David Miller wrote:
> From: Rick Jones <rick.jones2@hp.com>
> Date: Tue, 02 Sep 2008 09:40:46 -0700
>>Can one change the TCP maximum RTO to be smaller than specified in the specs?
> We always min-clamp the RTO at RTO calculation time in order to be
> compatible with BSD's coarse grained times.
But tuning TCP_RTO_MAX isn't permitted right? I'm drawing (perhaps
flawed) parallels/distinctions between what is/isn't permitted to tweak
for timers for one protocol versus another and wondering which may be a
case of sauce for the goose/gander.
rick jones
next prev parent reply other threads:[~2008-09-03 0:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.wTMiBcGRgw2fBtdHwtX7y0lkc8s@ifi.uio.no>
2008-08-04 19:43 ` ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 Robert Hancock
2008-08-04 20:37 ` Dushan Tcholich
2008-08-07 18:58 ` Francois Romieu
2008-08-10 19:00 ` Dushan Tcholich
2008-08-11 7:53 ` Dushan Tcholich
2008-08-30 1:48 ` Dushan Tcholich
2008-08-31 8:51 ` Dushan Tcholich
2008-08-31 17:05 ` Stephen Hemminger
2008-08-31 17:43 ` [Bridge] [RFC] bridge: STP timer management range checking Stephen Hemminger
2008-08-31 17:43 ` Stephen Hemminger
2008-08-31 22:02 ` [Bridge] " Alan Cox
2008-08-31 22:02 ` Alan Cox
2008-08-31 23:29 ` [Bridge] " Stephen Hemminger
2008-08-31 23:29 ` Stephen Hemminger
2008-09-01 8:38 ` [Bridge] " Alan Cox
2008-09-01 8:38 ` Alan Cox
2008-09-02 16:40 ` [Bridge] " Rick Jones
2008-09-02 16:40 ` Rick Jones
2008-09-02 23:41 ` [Bridge] " David Miller
2008-09-02 23:41 ` David Miller
2008-09-03 0:00 ` Rick Jones [this message]
2008-09-03 0:00 ` Rick Jones
2008-09-01 2:25 ` [Bridge] " Valdis.Kletnieks
2008-09-01 2:25 ` Valdis.Kletnieks
2008-09-03 0:28 ` [Bridge] " David Miller
2008-09-03 0:28 ` David Miller
2008-09-04 22:47 ` [Bridge] [PATCH] bridge: don't allow setting hello time to zero Stephen Hemminger
2008-09-04 22:47 ` Stephen Hemminger
2008-09-08 20:46 ` [Bridge] " David Miller
2008-09-08 20:46 ` David Miller
2008-09-08 21:35 ` [Bridge] " Dushan Tcholich
2008-09-08 21:35 ` Dushan Tcholich
2008-09-08 22:33 ` [Bridge] " Stephen Hemminger
2008-09-08 22:33 ` Stephen Hemminger
2008-08-31 19:14 ` ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 Dushan Tcholich
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=48BDD3A8.6070500@hp.com \
--to=rick.jones2@hp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dusanc@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@vyatta.com \
--cc=stephen.hemminger@vyatta.com \
/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.