From: Pete Heist <pete@heistp.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] proving out SCE
Date: Sat, 16 Mar 2019 17:21:13 +0100 [thread overview]
Message-ID: <0E91C3CA-10E5-4BA4-AA0C-87B70E295A0D@heistp.net> (raw)
In-Reply-To: <C41F0DCD-76F0-4CFA-9806-7A71674BED4F@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
Seeing the marks visually would be useful, even if it’s just to look at how the AQM marks it for now. It looks like tcptrace currently puts the text “CE” and “CWR CE” in the time-sequence graphs. This is where you’d want to see “SCE”?
Otherwise, I could extract the bits from Go and use some plotting lib or make a csv. I’ve had to parse pcaps before (https://github.com/heistp/wanonpcap <https://github.com/heistp/wanonpcap>). I just don’t know if you need to see the ECN bits alongside window sizes or other things...
> On Mar 16, 2019, at 3:58 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
> Also, a version of tcptrace that can plot SCE activity would be valuable. A plot of SCE marking proportion observed on the forward path, and some indication of any feedback path that exists.
>
> - Jonathan Morton
>
[-- Attachment #2: Type: text/html, Size: 1408 bytes --]
next prev parent reply other threads:[~2019-03-16 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 10:11 Pete Heist
2019-03-16 13:37 ` Jonathan Morton
2019-03-16 14:58 ` Jonathan Morton
2019-03-16 16:21 ` Pete Heist [this message]
2019-03-16 16:49 ` Jonathan Morton
2019-03-16 18:44 ` Pete Heist
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0E91C3CA-10E5-4BA4-AA0C-87B70E295A0D@heistp.net \
--to=pete@heistp.net \
--cc=chromatix99@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
/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