[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151019043907.GA11368@mininet-vm>
Date: Sun, 18 Oct 2015 21:39:07 -0700
From: Andrew Shewmaker <agshew@...il.com>
To: Yuchung Cheng <ycheng@...gle.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
Neal Cardwell <ncardwell@...gle.com>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next 2/7] tcp: track min RTT using windowed min-filter
On Wed, Oct 14, 2015 at 02:28:00AM -0700, Andrew Shewmaker wrote:
> On Fri, Oct 16, 2015 at 09:57:42PM -0700, Yuchung Cheng wrote:
> ...
> > diff --git a/include/linux/tcp.h b/include/linux/tcp.h
> > index 86a7eda..90edef5 100644
> > --- a/include/linux/tcp.h
> > +++ b/include/linux/tcp.h
> > @@ -217,6 +217,9 @@ struct tcp_sock {
> > u32 mdev_max_us; /* maximal mdev for the last rtt period */
> > u32 rttvar_us; /* smoothed mdev_max */
> > u32 rtt_seq; /* sequence number to update rttvar */
> > + struct rtt_meas {
> > + u32 rtt, ts; /* RTT in usec and sampling time in jiffies. */
> > + } rtt_min[3];
>
> First, thanks for all the work in this patch series. In particular,
> applying Kern's check to ca_seq_rtt_us should fix some bad behavior
> I've observed recently.
I'd have to run more tests to be sure, but net-next with this patch series
significantly improves upon the poor behavior I was seeing where randomly
dropped packets greatly limited the usefulness of RTTs as a signal of
congestion. I still see some measurements that exceed the amount of delay
possible from queue buildup, but fewer than before.
Thanks!
-Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists