From: David Miller <davem@davemloft.net>
To: francisyyan@gmail.com
Cc: netdev@vger.kernel.org, edumazet@google.com, soheil@google.com,
ncardwell@google.com, ycheng@google.com
Subject: Re: [PATCH net-next 1/2] tcp: measure rwnd-limited time
Date: Wed, 07 Sep 2016 17:27:42 -0700 (PDT) [thread overview]
Message-ID: <20160907.172742.1031784635164954011.davem@davemloft.net> (raw)
In-Reply-To: <1473211961-107223-1-git-send-email-francisyyan@gmail.com>
From: "Francis Y. Yan" <francisyyan@gmail.com>
Date: Tue, 6 Sep 2016 18:32:40 -0700
> diff --git a/include/linux/tcp.h b/include/linux/tcp.h
> index 7be9b12..f5b588e 100644
> --- a/include/linux/tcp.h
> +++ b/include/linux/tcp.h
> @@ -176,6 +176,7 @@ struct tcp_sock {
> * were acked.
> */
> struct u64_stats_sync syncp; /* protects 64bit vars (cf tcp_get_info()) */
> + seqcount_t seqcnt; /* proctects rwnd-limited-related vars, etc. */
>
> u32 snd_una; /* First byte we want an ack for */
> u32 snd_sml; /* Last byte of the most recently transmitted small packet */
> @@ -204,6 +205,8 @@ struct tcp_sock {
>
> u32 window_clamp; /* Maximal window to advertise */
> u32 rcv_ssthresh; /* Current window clamp */
> + struct skb_mstamp rwnd_limited_ts; /* Last timestamp limited by rwnd */
> + u64 rwnd_limited; /* Total time (us) limited by rwnd */
>
> /* Information of the most recently (s)acked skb */
> struct tcp_rack {
I understand completely the usefulness of this change, but wow that is a lot of
new TCP socket space taken up just to export some time values in tcp_info for
debugging and statistics.
next prev parent reply other threads:[~2016-09-08 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 1:32 [PATCH net-next 1/2] tcp: measure rwnd-limited time Francis Y. Yan
2016-09-07 1:32 ` [PATCH net-next 2/2] tcp: put a TLV list of TCP stats in error queue Francis Y. Yan
2016-09-07 5:04 ` Soheil Hassas Yeganeh
2016-09-07 14:22 ` Eric Dumazet
2016-09-07 5:07 ` [PATCH net-next 1/2] tcp: measure rwnd-limited time Soheil Hassas Yeganeh
2016-09-07 14:19 ` Eric Dumazet
2016-09-08 0:27 ` David Miller [this message]
2016-09-08 15:31 ` Yuchung Cheng
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=20160907.172742.1031784635164954011.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=francisyyan@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;
as well as URLs for NNTP newsgroup(s).