From: tsuna <tsunanet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: kuznet@ms2.inr.ac.ru, pekkas@netcore.fi, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, hagen@jauu.net,
eric.dumazet@gmail.com,
alexander.zimmermann@comsys.rwth-aachen.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tcp: Implement a two-level initial RTO as per draft RFC 2988bis-02.
Date: Wed, 18 May 2011 21:33:21 -0700 [thread overview]
Message-ID: <BANLkTikQEq9+YkJHcTe3PWnRvh7AN=VVWA@mail.gmail.com> (raw)
In-Reply-To: <20110519.001426.2119532755281545481.davem@davemloft.net>
On Wed, May 18, 2011 at 9:14 PM, David Miller <davem@davemloft.net> wrote:
> The IETF draft has a requirement that we fallback to 3 seconds if the
> initial RTO is 1 second.
>
> Nothing in your facilities ensure this, or provide a way for the
> kernel to make sure this is the case.
Not sure to understand what you're saying. If tcp_initial_rto = 1000
and tcp_initial_fallback_rto = 3000, then you get exactly the behavior
the draft describes. The knobs simply allow you to either revert to
today's behavior or use other settings that would make more sense in
your environment (e.g. very high RTT). Are you concerned about cases
where, say, tcp_initial_fallback_rto < tcp_initial_rto?
> And for other values of initial RTO, what fallback is appropriate?
Presumably if the user decides to tweak these knobs, they'll know
what's appropriate for their environment. Or are you suggesting that
one value be derived from the other? (e.g. tcp_initial_fallback_rto =
3 * tcp_initial_rto)
> As a result of all of this, I do not really think this is something
> the user should control at all.
>
> I really would rather see the initial RTO be static and be set to 1
> with fallback RTO of 3.
I can also provide a simple patch for this if you want to start from
there. And then maybe we can discuss having a runtime knob some more
:-)
--
Benoit "tsuna" Sigoure
Software Engineer @ www.StumbleUpon.com
next prev parent reply other threads:[~2011-05-19 4:33 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 7:40 [PATCH] tcp: Expose the initial RTO via a new sysctl Benoit Sigoure
2011-05-17 7:40 ` Benoit Sigoure
2011-05-17 8:01 ` Alexander Zimmermann
2011-05-17 8:34 ` Eric Dumazet
2011-05-17 8:07 ` Eric Dumazet
2011-05-17 11:02 ` Hagen Paul Pfeifer
2011-05-17 11:02 ` Hagen Paul Pfeifer
2011-05-17 12:20 ` Eric Dumazet
2011-05-18 10:43 ` Benoit Sigoure
2011-05-18 19:26 ` David Miller
2011-05-18 19:40 ` tsuna
2011-05-18 19:52 ` David Miller
2011-05-18 20:20 ` Hagen Paul Pfeifer
2011-05-18 20:23 ` David Miller
2011-05-18 20:27 ` Hagen Paul Pfeifer
2011-05-20 10:27 ` H.K. Jerry Chu
2011-05-20 11:00 ` Hagen Paul Pfeifer
2011-05-20 11:00 ` Hagen Paul Pfeifer
2011-05-20 12:37 ` Alan Cox
2011-05-21 0:06 ` H.K. Jerry Chu
2011-05-31 14:48 ` tsuna
2011-05-31 15:25 ` Hagen Paul Pfeifer
2011-05-31 15:25 ` Hagen Paul Pfeifer
2011-05-31 15:28 ` tsuna
2011-05-31 15:43 ` Hagen Paul Pfeifer
2011-05-31 15:43 ` Hagen Paul Pfeifer
2011-05-19 2:22 ` [PATCH] tcp: Implement a two-level initial RTO as per draft RFC 2988bis-02 Benoit Sigoure
2011-05-19 2:22 ` Benoit Sigoure
2011-05-19 2:36 ` David Miller
2011-05-19 3:56 ` tsuna
2011-05-19 4:14 ` David Miller
2011-05-19 4:33 ` tsuna [this message]
2011-05-19 5:46 ` David Miller
2011-05-19 6:36 ` [PATCH] tcp: Lower the initial RTO to 1s " Benoit Sigoure
2011-05-19 6:36 ` Benoit Sigoure
2011-05-19 17:42 ` Yuchung Cheng
2011-05-19 6:47 ` Benoit Sigoure
2011-05-19 6:47 ` Benoit Sigoure
2011-05-19 20:16 ` David Miller
2011-05-19 6:10 ` [PATCH] tcp: Implement a two-level initial RTO " Alexander Zimmermann
2011-05-19 6:25 ` tsuna
2011-05-19 6:36 ` Alexander Zimmermann
2011-05-19 6:42 ` tsuna
2011-05-19 6:52 ` Alexander Zimmermann
2011-05-19 7:07 ` tsuna
2011-05-19 8:02 ` Hagen Paul Pfeifer
2011-05-19 8:02 ` Hagen Paul Pfeifer
2011-05-19 16:40 ` tsuna
2011-05-19 16:55 ` Alexander Zimmermann
2011-05-19 17:11 ` tsuna
2011-05-19 19:27 ` David Miller
2011-05-19 20:30 ` tsuna
2011-05-20 2:01 ` [PATCH] tcp: Expose the initial RTO via a new sysctl H.K. Jerry Chu
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='BANLkTikQEq9+YkJHcTe3PWnRvh7AN=VVWA@mail.gmail.com' \
--to=tsunanet@gmail.com \
--cc=alexander.zimmermann@comsys.rwth-aachen.de \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hagen@jauu.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--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 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.