General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, Matt Mathis <mattmathis@google.com>
Cc: Randall Meyer <rrm@apple.com>
Subject: [Bloat] Getting TCP_INFO stats in apache traffic server
Date: Sun, 20 Jun 2021 22:06:19 -0700	[thread overview]
Message-ID: <CAA93jw6vq0FXGi2DDgtUZW6RRQq5_U7RZ7ctrYg506SFhBq3uQ@mail.gmail.com> (raw)

It's been a decade since I had to patch web100 into the kernel and
matt told me recently
that tons of it HAD finally ended up in the linux kernel, so I looked,
thinking I'd at the very least patch up
apache traffic server and netperf to start reporting that information.
Wow! what a goldmine!

Getting out the ECN CE stats is now easy. The min_rtt stat looks
useful, but I wanted also a max_rtt
stat or some way to calculate it?

apache traffic server currently reports only:

    ret = TSTextLogObjectWrite(config->log, "%s %s %s %u %u %u %u %u
%u %u %u %u %u %u %u %u %u %u", event_name, client_str,
                               server_str, info.tcpi_rtt,
info.tcpi_rttvar, info.tcpi_last_data_sent, info.tcpi_last_data_recv,
                               info.tcpi_snd_cwnd,
info.tcpi_snd_ssthresh, info.tcpi_rcv_ssthresh, info.tcpi_unacked,
                               info.tcpi_sacked, info.tcpi_lost,
info.tcpi_retrans, info.tcpi_fackets, info.tcpi_total_retrans,
                               info.tcpi_data_segs_in, info.tcpi_data_segs_out,

This is what linux 5.11 now can get back to you. Anyone see anything
exceptionally useful worth logging
here?

       __u8    tcpi_state;
        __u8    tcpi_ca_state;
        __u8    tcpi_retransmits;
        __u8    tcpi_probes;
        __u8    tcpi_backoff;
        __u8    tcpi_options;
        __u8    tcpi_snd_wscale : 4, tcpi_rcv_wscale : 4;
        __u8    tcpi_delivery_rate_app_limited:1, tcpi_fastopen_client_fail:2;

        __u32   tcpi_rto;
        __u32   tcpi_ato;
        __u32   tcpi_snd_mss;
        __u32   tcpi_rcv_mss;

        __u32   tcpi_unacked;
        __u32   tcpi_sacked;
        __u32   tcpi_lost;
        __u32   tcpi_retrans;
        __u32   tcpi_fackets;

        /* Times. */
        __u32   tcpi_last_data_sent;
        __u32   tcpi_last_ack_sent;     /* Not remembered, sorry. */
        __u32   tcpi_last_data_recv;
        __u32   tcpi_last_ack_recv;

        /* Metrics. */
        __u32   tcpi_pmtu;
        __u32   tcpi_rcv_ssthresh;
        __u32   tcpi_rtt;
        __u32   tcpi_rttvar;
        __u32   tcpi_snd_ssthresh;
        __u32   tcpi_snd_cwnd;
        __u32   tcpi_advmss;
        __u32   tcpi_reordering;

        __u32   tcpi_rcv_rtt;
        __u32   tcpi_rcv_space;

        __u32   tcpi_total_retrans;

        __u64   tcpi_pacing_rate;
        __u64   tcpi_max_pacing_rate;
        __u64   tcpi_bytes_acked;    /* RFC4898 tcpEStatsAppHCThruOctetsAcked */
        __u64   tcpi_bytes_received; /* RFC4898
tcpEStatsAppHCThruOctetsReceived */
        __u32   tcpi_segs_out;       /* RFC4898 tcpEStatsPerfSegsOut */
        __u32   tcpi_segs_in;        /* RFC4898 tcpEStatsPerfSegsIn */

        __u32   tcpi_notsent_bytes;
        __u32   tcpi_min_rtt;
        __u32   tcpi_data_segs_in;      /* RFC4898 tcpEStatsDataSegsIn */
        __u32   tcpi_data_segs_out;     /* RFC4898 tcpEStatsDataSegsOut */

        __u64   tcpi_delivery_rate;

        __u64   tcpi_busy_time;      /* Time (usec) busy sending data */
        __u64   tcpi_rwnd_limited;   /* Time (usec) limited by receive window */
        __u64   tcpi_sndbuf_limited; /* Time (usec) limited by send buffer */

        __u32   tcpi_delivered;
        __u32   tcpi_delivered_ce;

        __u64   tcpi_bytes_sent;     /* RFC4898 tcpEStatsPerfHCDataOctetsOut */
        __u64   tcpi_bytes_retrans;  /* RFC4898 tcpEStatsPerfOctetsRetrans */
        __u32   tcpi_dsack_dups;     /* RFC4898 tcpEStatsStackDSACKDups */
        __u32   tcpi_reord_seen;     /* reordering events seen */

        __u32   tcpi_rcv_ooopack;    /* Out-of-order packets received */
        __u32   tcpi_snd_wnd;        /* peer's advertised receive window after
                                      * scaling (bytes)
                                      */



-- 
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/

Dave Täht CTO, TekLibre, LLC

                 reply	other threads:[~2021-06-21  5:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6vq0FXGi2DDgtUZW6RRQq5_U7RZ7ctrYg506SFhBq3uQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=mattmathis@google.com \
    --cc=rrm@apple.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