From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: stephen@networkplumber.org, ja@ssi.bg, ycheng@google.com,
netdev@vger.kernel.org, ncardwell@google.com, brakmo@google.com
Subject: Re: [PATCH v7 net-next 2/2] tcp: switch rtt estimations to usec resolution
Date: Wed, 26 Feb 2014 17:04:39 -0500 (EST) [thread overview]
Message-ID: <20140226.170439.506202474296777480.davem@davemloft.net> (raw)
In-Reply-To: <1393452168.26794.8.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 26 Feb 2014 14:02:48 -0800
> From: Eric Dumazet <edumazet@google.com>
>
> Upcoming congestion controls for TCP require usec resolution for RTT
> estimations. Millisecond resolution is simply not enough these days.
>
> FQ/pacing in DC environments also require this change for finer control
> and removal of bimodal behavior due to the current hack in
> tcp_update_pacing_rate() for 'small rtt'
>
> TCP_CONG_RTT_STAMP is no longer needed.
>
> As Julian Anastasov pointed out, we need to keep user compatibility :
> tcp_metrics used to export RTT and RTTVAR in msec resolution,
> so we added RTT_US and RTTVAR_US. An iproute2 patch is needed
> to use the new attributes if provided by the kernel.
>
...
> With help from Julian Anastasov, Stephen Hemminger and Yuchung Cheng
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Acked-by: Neal Cardwell <ncardwell@google.com>
Applied, thanks everyone.
next prev parent reply other threads:[~2014-02-26 22:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 6:38 [PATCH net-next] tcp: switch rtt estimations to usec resolution Eric Dumazet
2014-02-23 7:36 ` Julian Anastasov
2014-02-23 17:55 ` Eric Dumazet
2014-02-23 18:50 ` [PATCH v2 " Eric Dumazet
2014-02-23 19:19 ` Yuchung Cheng
2014-02-23 21:41 ` Eric Dumazet
2014-02-24 4:42 ` [PATCH v3 " Eric Dumazet
2014-02-24 17:58 ` Eric Dumazet
2014-02-24 18:24 ` [PATCH v4 " Eric Dumazet
2014-02-24 20:47 ` Julian Anastasov
2014-02-24 22:13 ` Eric Dumazet
2014-02-24 23:01 ` Julian Anastasov
2014-02-24 23:31 ` [PATCH v5 " Eric Dumazet
2014-02-24 23:51 ` Stephen Hemminger
2014-02-25 0:15 ` David Miller
2014-02-25 1:11 ` Eric Dumazet
2014-02-25 1:38 ` Eric Dumazet
2014-02-25 6:22 ` [PATCH v6 net-next 1/2] net: add skb_mstamp infrastructure Eric Dumazet
2014-02-25 9:51 ` David Laight
2014-02-25 12:21 ` Eric Dumazet
2014-02-26 20:02 ` David Miller
2014-02-26 20:29 ` Eric Dumazet
2014-02-26 22:02 ` [PATCH v7 " Eric Dumazet
2014-02-26 22:04 ` David Miller
2014-02-25 6:22 ` [PATCH v6 net-next 2/2] tcp: switch rtt estimations to usec resolution Eric Dumazet
2014-02-25 17:46 ` Neal Cardwell
2014-02-25 18:17 ` Eric Dumazet
2014-02-25 19:13 ` Neal Cardwell
2014-02-26 22:02 ` [PATCH v7 " Eric Dumazet
2014-02-26 22:04 ` David Miller [this message]
2014-02-27 1:09 ` Stephen Hemminger
2014-02-27 1:21 ` Rick Jones
2014-02-27 9:57 ` David Laight
2014-02-27 2:25 ` Eric Dumazet
2014-02-24 22:19 ` [PATCH v4 net-next] " Eric Dumazet
2014-02-28 5:20 ` [PATCH v2 " Andi Kleen
2014-02-28 6:14 ` Eric Dumazet
2014-02-28 13:31 ` Andi Kleen
2014-02-28 13:51 ` Eric Dumazet
2014-02-23 19:11 ` [PATCH " Julian Anastasov
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=20140226.170439.506202474296777480.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brakmo@google.com \
--cc=eric.dumazet@gmail.com \
--cc=ja@ssi.bg \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=ycheng@google.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;
as well as URLs for NNTP newsgroup(s).