From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: ruben@vfn-nrw.de, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Status of sch_cake and sctp with ECN
Date: Wed, 10 Oct 2018 06:48:01 -0700 [thread overview]
Message-ID: <CAA93jw7A37UWOx4hr+-UEiE9ARvcQTqa72CY504uT5BAmHcyxg@mail.gmail.com> (raw)
In-Reply-To: <AFEC3BB3-E888-4113-8D13-67B227871C00@gmail.com>
It turns out that years ago we incorporated an sctp test into flent
but it doesn't work.
also, I tend to compile netperf with --enable-demo --enable-sctp - but
that *silently* fails unless libsctp is installed.
Anyway flent-fremont's netperf server now supports sctp, and my
firewall for ipv6 doesn't block sctp, and lo and behold,
sctp negotiates ecn.
It does this independent of the setting of the net.ipv4.tcp_ecn
variable. It always negotiates ecn.
However, its congestion control (at least in the framework of the
netperf test) is just miserable, the SCTP_STREAM test
has serious issues trying to saturate a 20Mbit link over 60 seconds.
the STREAM_STREAM_MULTI test does, though,
and you can see cake making CE markings on it. I don't have sufficient
tools or time to look into whether it's doing the right things or
not. If anyone cares, a packet cap is up at:
http://flent-fremont.bufferbloat.net/~d/sctp/sctp.cap
On the other hand, I'm perfectly happy to have a standard, non-greedy,
reliable, protocol, one capable of multihoming, actually work from
within my home, over ipv6. It feels like the 80s, back when the future
for new protocols looked bright, and disco was king.
d@dancer:~/sctp$ Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 4096 60.00 4.96
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 4096 60.00 4.89
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 4096 60.00 4.89
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 4096 60.00 4.91
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 212992 60.01 0.03
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 212992 60.01 0.03
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 212992 60.01 0.09
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
212992 212992 212992 60.01 0.03
prev parent reply other threads:[~2018-10-10 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 8:45 Ruben
2018-10-08 5:06 ` Dave Taht
2018-10-08 5:16 ` Jonathan Morton
2018-10-10 13:48 ` Dave Taht [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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7A37UWOx4hr+-UEiE9ARvcQTqa72CY504uT5BAmHcyxg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=ruben@vfn-nrw.de \
/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