From: Dave Taht <dave.taht@gmail.com>
To: ruben@vfn-nrw.de
Cc: Cake List <cake@lists.bufferbloat.net>, ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] [Cake] Status of sch_cake and sctp with ECN
Date: Sun, 7 Oct 2018 22:06:35 -0700 [thread overview]
Message-ID: <CAA93jw5aquUf_WqA=J10qKzNwgDoV4RRhKXcsYQdiR5AM-tg=w@mail.gmail.com> (raw)
In-Reply-To: <c1cff3d3-f0b9-4098-9f32-204314a3eb7c@email.android.com>
On Sun, Oct 7, 2018 at 9:46 PM Ruben <ruben@vfn-nrw.de> wrote:
>
> Hey guys,
>
> I googled this but I found no answers. RFC4960 (the sctp RFC) is mentioning ECN, but just in the appendix. I was wondering if the Linux library has ECN support, and how one might active it (as socket option or as system setting?)
Pretty good question. The added reliability of ecn would benefit sctp
applications. There's two ways to get sctp out of linux, the kernel
way and a userspace way. Kernel I thought was the most common. Netperf
has support for it. 4+ years back I'd mostly tested sctp over ipv6
and at least from the kernel code in net/sctp/ipv6 it appears to mark
packets as ecn capable, but I wasn't looking at the time. whether the
congestion control in sctp is currently working worth a damn, don't
know.
So I can quickly setup a server to test this over ipv6 this week.
>and if this tags are currently supported to be handled by sch_cake?
ecn capability is a property of any protocol built on top of ip, tcp,
udp, sctp, udp_lite, etc.
> Hope someone got a bit more overview about this, than me, without digging into code documentations.
>
> Thanks in advance!
>
>
> Best regards
>
> Ruben
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
parent reply other threads:[~2018-10-08 5:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <c1cff3d3-f0b9-4098-9f32-204314a3eb7c@email.android.com>]
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='CAA93jw5aquUf_WqA=J10qKzNwgDoV4RRhKXcsYQdiR5AM-tg=w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=ecn-sane@lists.bufferbloat.net \
--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