From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] any ideas to help solve tcp-prague's problems?
Date: Mon, 1 Apr 2019 08:29:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1904010827270.14375@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw5dO1_D1panFPNQnax5jRDPKn8NEvQE9zdE8HmVmujMBw@mail.gmail.com>
On Mon, 1 Apr 2019, Dave Taht wrote:
> see:
>
> https://github.com/L4STeam/tcp-prague/issues/2
Just to comment that single-queue ECN-marking FIFO might not be available
today, but if I get my way to get people to start configuring their
existing equipment correctly, this would be a lot more common in the
future.
A lot of devices do not currently have the "mark ECN" as option in their
RED behaviour, but some do.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2019-04-01 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 4:37 Dave Taht
2019-04-01 6:29 ` Mikael Abrahamsson [this message]
2019-04-01 6:31 ` Dave Taht
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=alpine.DEB.2.20.1904010827270.14375@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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