Ethernet Bridge development
 help / color / mirror / Atom feed
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

  reply	other threads:[~2008-09-03  0:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.wTMiBcGRgw2fBtdHwtX7y0lkc8s@ifi.uio.no>
     [not found] ` <48975BD3.6040709@shaw.ca>
     [not found]   ` <a08621850808041337k1d1deb6fk78098d9fcd4930dd@mail.gmail.com>
     [not found]     ` <20080807185802.GA16327@electric-eye.fr.zoreil.com>
     [not found]       ` <a08621850808101200n220afd2dve58abe67830b7a4f@mail.gmail.com>
     [not found]         ` <a08621850808110053j5cbf23e6xdf52c9e7440abf19@mail.gmail.com>
     [not found]           ` <a08621850808291848q5660148fx57d576ecfcbfce8@mail.gmail.com>
     [not found]             ` <a08621850808310151o143845h195a8658d02270d9@mail.gmail.com>
     [not found]               ` <20080831100537.6929c51e@extreme>
2008-08-31 17:43                 ` [Bridge] [RFC] bridge: STP timer management range checking Stephen Hemminger
2008-08-31 22:02                   ` Alan Cox
2008-08-31 23:29                     ` Stephen Hemminger
2008-09-01  8:38                       ` Alan Cox
2008-09-02 16:40                         ` Rick Jones
2008-09-02 23:41                           ` David Miller
2008-09-03  0:00                             ` Rick Jones [this message]
2008-09-01  2:25                   ` Valdis.Kletnieks
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-08 20:46                     ` David Miller
2008-09-08 21:35                       ` Dushan Tcholich
2008-09-08 22:33                         ` Stephen Hemminger

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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox