Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	Cake List <cake@lists.bufferbloat.net>,
	Pete Heist <pete@heistp.net>
Subject: Re: [Cake] Sce In cake testers wanted
Date: Sun, 24 Mar 2019 00:54:22 +0100	[thread overview]
Message-ID: <CAA93jw6BMggHXcYoqfFS2e0iuB54iMr+q+BWv720Z4zfaMb5gw@mail.gmail.com> (raw)
In-Reply-To: <3F3F78F9-8F97-42F2-9005-F8449489BECF@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]

There are two openwrt routers on the boat.

On Sun, Mar 24, 2019, 12:53 AM Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 23 Mar, 2019, at 10:28 pm, Kevin Darbyshire-Bryant <
> kevin@darbyshire-bryant.me.uk> wrote:
> >
> > Sent a github PR to make it build - not run it yet.
>
> LGTM, so I approved it.  I've reached the "bufferboat" and started to
> settle in, met Rod and Pete…
>
> I brought a Pi Zero W with me as a basic Linux test environment, but I
> need to find a mini to macro HDMI adapter to make it work with this TV.
> Pete says he'll look for one to bring over tomorrow.
>
> So now we probably have *two* working middlebox implementations, using
> different approaches, but we need a visualisation tool (hi Pete) and some
> sort of working TCP that uses it (whether using the sqrt rule or the 1/n
> rule, doesn't really matter - but preferably examples of both).  For the
> latter, we can temporarily get away with inferring stuff from standard
> tcptrace.  If there's a working implementation of AccECN for the feedback
> path, we might as well use that for demo purposes.
>
> I want to be able to demonstrate SCE actually working as designed, in a
> single-queue implementation, to answer the main argument that some of the
> L4S folks have latched onto.  But I don't know how soon we'll be able to
> manage that.
>
>  - Jonathan Morton
>
>

[-- Attachment #2: Type: text/html, Size: 1789 bytes --]

  reply	other threads:[~2019-03-23 23:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23 19:15 Dave Taht
2019-03-23 21:28 ` Kevin Darbyshire-Bryant
2019-03-23 23:53   ` Jonathan Morton
2019-03-23 23:54     ` Dave Taht [this message]
2019-03-23 23:58       ` Jonathan Morton
2019-03-24  7:37         ` Pete Heist
2019-03-24  8:45           ` Jonathan Morton
2019-03-24  8:55             ` [Cake] The two SCE tests I have in mind Dave Taht
2019-03-24  9:30               ` Luca Muscariello
2019-03-24 10:30                 ` Dave Taht
2019-03-24 12:33                   ` Dave Taht
2019-03-24 22:31                   ` Sebastian Moeller
2019-03-24 11:05               ` Pete Heist
2019-03-24 11:08                 ` Jonathan Morton
2019-03-24 11:21                   ` Pete Heist
2019-03-24 12:32                   ` [Cake] [Ecn-sane] " Michael Richardson
2019-04-01 16:02                     ` Stephen Hemminger
2019-04-01 17:21                       ` Dave Taht
2019-04-02 13:36                       ` Rodney W. Grimes
2019-03-24 21:00   ` [Cake] Sce In cake testers wanted Kevin Darbyshire-Bryant

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=CAA93jw6BMggHXcYoqfFS2e0iuB54iMr+q+BWv720Z4zfaMb5gw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=kevin@darbyshire-bryant.me.uk \
    --cc=pete@heistp.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