From: David Miller <davem@davemloft.net>
To: weiwan@google.com
Cc: netdev@vger.kernel.org, edumazet@google.com,
ncardwell@google.com, soheil@google.com, ycheng@google.com
Subject: Re: [PATCH v2 net-next 0/5] tcp: add 4 new stats
Date: Wed, 01 Aug 2018 09:56:30 -0700 (PDT) [thread overview]
Message-ID: <20180801.095630.2185828024414600638.davem@davemloft.net> (raw)
In-Reply-To: <20180801004624.154346-1-tracywwnj@gmail.com>
From: Wei Wang <weiwan@google.com>
Date: Tue, 31 Jul 2018 17:46:19 -0700
> From: Wei Wang <weiwan@google.com>
>
> This patch series adds 3 RFC4898 stats:
> 1. tcpEStatsPerfHCDataOctetsOut
> 2. tcpEStatsPerfOctetsRetrans
> 3. tcpEStatsStackDSACKDups
> and an addtional stat to record the number of data packet reordering
> events seen:
> 4. tcp_reord_seen
>
> Together with the existing stats, application can use them to measure
> the retransmission rate in bytes, exclude spurious retransmissions
> reflected by DSACK, and keep track of the reordering events on live
> connections.
> In particular the networks with different MTUs make bytes-based loss stats
> more useful. Google servers have been using these stats for many years to
> instrument transport and network performance.
>
> Note: The first patch is a refactor to add a helper to calculate
> opt_stats size in order to make later changes cleaner.
Series applied, thank you.
prev parent reply other threads:[~2018-08-01 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 0:46 [PATCH v2 net-next 0/5] tcp: add 4 new stats Wei Wang
2018-08-01 0:46 ` [PATCH v2 net-next 1/5] tcp: add a helper to calculate size of opt_stats Wei Wang
2018-08-01 0:46 ` [PATCH v2 net-next 2/5] tcp: add data bytes sent stats Wei Wang
2018-08-01 0:46 ` [PATCH v2 net-next 3/5] tcp: add data bytes retransmitted stats Wei Wang
2018-08-01 0:46 ` [PATCH v2 net-next 4/5] tcp: add dsack blocks received stats Wei Wang
2018-08-01 0:46 ` [PATCH v2 net-next 5/5] tcp: add stat of data packet reordering events Wei Wang
2018-08-01 16:56 ` David Miller [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=20180801.095630.2185828024414600638.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.com \
--cc=weiwan@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;
as well as URLs for NNTP newsgroup(s).