From: Stephen Hemminger <stephen@networkplumber.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
Yuchung Cheng <ycheng@google.com>,
Neal Cardwell <ncardwell@google.com>
Subject: Re: [PATCH iproute2] ss: add more TCP_INFO components
Date: Tue, 25 Jun 2013 13:33:52 -0700 [thread overview]
Message-ID: <20130625133352.6d10797a@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1372192157.3301.118.camel@edumazet-glaptop>
On Tue, 25 Jun 2013 13:29:17 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Allow ss -i to display more TCP informations :
>
> unacked:N Number of un-acked packets
> retrans:X/Y X: number of outstanding retransmit packets
> Y: total number of retransmits for the session
> lost:N Number of lost packets (tcpi_lost)
> sacked:N Number of sacked packets (tcpi_sacked)
> facked:N Number of facked packets (tcpi_facked)
> reordering:N Reordering level (if different of 3)
>
> Example :
>
> $ ss -emoi dst 10.7.7.83
> tcp ESTAB 0 1154056 10.7.7.84:54127 10.7.7.83:34342
> timer:(on,200ms,0) ino:57003 sk:ffff88063c51d0c0 <->
> skmem:(r0,rb89280,t0,tb2097152,f726504,w1436184,o0,bl0) ts sack cubic
> wscale:7,6 rto:310 rtt:107.375/1 mss:1448 cwnd:568 ssthresh:108 send
> 61.3Mbps unacked:568 retrans:0/21 reordering:127 rcv_space:29200
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Yuchung Cheng <ycheng@google.com>
> Cc: Neal Cardwell <ncardwell@google.com>
Applied
prev parent reply other threads:[~2013-06-25 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 20:29 [PATCH iproute2] ss: add more TCP_INFO components Eric Dumazet
2013-06-25 20:33 ` 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=20130625133352.6d10797a@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.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).