From: Stephen Hemminger <stephen@networkplumber.org>
To: Craig Gallek <kraig@google.com>
Cc: edumazet@google.com, mleitner@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] ss: add support for segs_in and segs_out
Date: Thu, 25 Jun 2015 23:52:04 -0400 [thread overview]
Message-ID: <20150625235204.53d39594@uryu.home.lan> (raw)
In-Reply-To: <1432666481-1582-1-git-send-email-kraig@google.com>
On Tue, 26 May 2015 14:54:41 -0400
Craig Gallek <kraig@google.com> wrote:
> Two new tcp_info fields: tcpi_segs_in and tcpi_segs_out.
> (2efd055c53c06b7e89c167c98069bab9afce7e59)
>
> ~: ss -ti src :22
> cubic wscale:7,6 rto:201 rtt:0.244/0.012 ato:40 mss:1418 cwnd:21 bytes_acked:80605 bytes_received:20491 segs_out:414 segs_in:600 send 976.3Mbps lastsnd:23 lastrcv:23 lastack:22 pacing_rate 1952.7Mbps rcv_rtt:98 rcv_space:28960
>
> Signed-off-by: Craig Gallek <kraig@google.com>
Applied to net-next branch
prev parent reply other threads:[~2015-06-26 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 18:54 [PATCH iproute2] ss: add support for segs_in and segs_out Craig Gallek
2015-05-26 19:01 ` Marcelo Ricardo Leitner
2015-06-26 3:52 ` Stephen Hemminger [this message]
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=20150625235204.53d39594@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=edumazet@google.com \
--cc=kraig@google.com \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.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 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).