Netdev List
 help / color / mirror / Atom feed
From: Thomas Higdon <tph@fb.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Dave Jones <dsj@fb.com>, Eric Dumazet <edumazet@google.com>,
	Dave Taht <dave.taht@gmail.com>,
	Yuchung Cheng <ycheng@google.com>,
	Soheil Hassas Yeganeh <soheil@google.com>
Subject: Re: [PATCH v5 1/2] tcp: Add TCP_INFO counter for packets received out-of-order
Date: Mon, 16 Sep 2019 17:42:39 +0000	[thread overview]
Message-ID: <20190916174220.GA41212@tph-mbp> (raw)
In-Reply-To: <CADVnQynfwJ8HWstz-HAa7AMOGRhDC7nqKwMCKpe2Fvm7kUQgkA@mail.gmail.com>

On Sat, Sep 14, 2019 at 11:43:25AM -0400, Neal Cardwell wrote:
> On Fri, Sep 13, 2019 at 7:23 PM Thomas Higdon <tph@fb.com> wrote:
> >
> > For receive-heavy cases on the server-side, we want to track the
> > connection quality for individual client IPs. This counter, similar to
> > the existing system-wide TCPOFOQueue counter in /proc/net/netstat,
> > tracks out-of-order packet reception. By providing this counter in
> > TCP_INFO, it will allow understanding to what degree receive-heavy
> > sockets are experiencing out-of-order delivery and packet drops
> > indicating congestion.
> >
> > Please note that this is similar to the counter in NetBSD TCP_INFO, and
> > has the same name.
> >
> > Also note that we avoid increasing the size of the tcp_sock struct by
> > taking advantage of a hole.
> >
> > Signed-off-by: Thomas Higdon <tph@fb.com>
> > ---
> > changes since v4:
> >  - optimize placement of rcv_ooopack to avoid increasing tcp_sock struct
> >    size
> 
> 
> Acked-by: Neal Cardwell <ncardwell@google.com>
> 
> Thanks, Thomas, for adding this!
> 
> After this is merged, would you mind sending a patch to add support to
> the "ss" command line tool to print these 2 new fields?
> 
> My favorite recent example of such a patch to ss is Eric's change:
>   https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/misc/ss.c?id=5eead6270a19f00464052d4084f32182cfe027ff

Yes, and thank you for the help in getting this into a good state!

From looking at that "ss" patch, it seems like we would need to wait
until iproute2-next's include/uapi/linux/tcp.h has received a merge from
kernel net-next before we'd be able to apply a patch for "ss" that uses
the new fields.

In the meantime, as you've asked, I will go ahead and send a patch for
iproute2-next's "ss" with the assumption that these tcpinfo changes have
already been merged.

  reply	other threads:[~2019-09-16 17:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 23:23 [PATCH v5 1/2] tcp: Add TCP_INFO counter for packets received out-of-order Thomas Higdon
2019-09-13 23:23 ` [PATCH v5 2/2] tcp: Add snd_wnd to TCP_INFO Thomas Higdon
2019-09-13 23:36   ` Yuchung Cheng
2019-09-14 15:45   ` Neal Cardwell
2019-09-14 17:57     ` Soheil Hassas Yeganeh
2019-09-16 14:39   ` David Miller
2019-09-14 15:43 ` [PATCH v5 1/2] tcp: Add TCP_INFO counter for packets received out-of-order Neal Cardwell
2019-09-16 17:42   ` Thomas Higdon [this message]
2019-09-16 14:39 ` David Miller

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=20190916174220.GA41212@tph-mbp \
    --to=tph@fb.com \
    --cc=dave.taht@gmail.com \
    --cc=dsj@fb.com \
    --cc=edumazet@google.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=soheil@google.com \
    --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