[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161128.161906.1900426045355871354.davem@davemloft.net>
Date: Mon, 28 Nov 2016 16:19:06 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: ycheng@...gle.com
Cc: soheil@...gle.com, francisyyan@...il.com, netdev@...r.kernel.org,
ncardwell@...gle.com, edumazet@...gle.com
Subject: Re: [PATCH net-next 0/6] tcp: sender chronographs instrumentation
From: Yuchung Cheng <ycheng@...gle.com>
Date: Sat, 26 Nov 2016 12:10:10 -0800
> This patch set provides instrumentation on TCP sender limitations.
> While developing the BBR congestion control, we noticed that TCP
> sending process is often limited by factors unrelated to congestion
> control: insufficient sender buffer and/or insufficient receive
> window/buffer to saturate the network bandwidth. Unfortunately these
> limits are not visible to the users and often the poor performance
> is attributed to the congestion control of choice.
>
> Thie patch aims to help users get the high level understanding of
> where sending process is limited by, similar to the TCP_INFO design.
> It is not to replace detailed kernel tracing and instrumentation
> facilities.
>
> In addition this patch set provides a new option to the timestamping
> work to instrument these limits on application data unit. For exampe,
> one can use SO_TIMESTAMPING and this patch set to measure the how
> long a particular HTTP response is limited by small receive window.
>
> Patch set was initially written by Francis Yan then polished
> by Yuchung Cheng, with lots of help from Eric Dumazet and Soheil
> Hassas Yeganeh.
Looks great, series applied, thanks!
Powered by blists - more mailing lists