From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Aaron Wood <woody77@gmail.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] fq_pie for linux
Date: Tue, 11 Dec 2018 12:35:58 -0800 [thread overview]
Message-ID: <CAA93jw5YJsDxJod5yKYTA8h1yPqFbxxcVuuDj5WuD-njSbaAFA@mail.gmail.com> (raw)
In-Reply-To: <87o99rizii.fsf@toke.dk>
On Tue, Dec 11, 2018 at 12:23 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Jonathan Morton <chromatix99@gmail.com> writes:
>
> >> On 11 Dec, 2018, at 8:32 pm, Aaron Wood <woody77@gmail.com> wrote:
> >>
> >> With all the variants of fq+AQM, maybe decoupling the FQ part and the
> >> AQM part would be worthwhile, instead of reimplementing it for each
> >> variant...
> >>
> >> That's a great idea, Toke. There are a lot of places where I think it could work well, especially if it took a pluggable hash function for the hashing (at which point it's very general-purpose, and works on all sorts of different kinds of packets and workloads). That would let it be used for userspace VPN links (as an example), or within QUIC (or similar), where the kernel can't see the embedded flows that are hidden by the TLS encryption.
> >>
> >> And having it pluggable in the kernel would also allow IPSec to work
> >> without bloat (last I checked it was horribly bufferbloated, but that
> >> was ~5 years ago).
> >
> > I wonder if it's worth extracting the triple-isolate and
> > set-associative hash logic from Cake for this purpose? The interface
> > to COBALT is clean enough to be replaced by other AQMs relatively
> > easily.
>
> There's already a reusable FQ structure in the kernel (which is what the
> WiFi stack uses), which is partially modelled on Cake's tins. I had half
> a mind to try to have the two converge; Cake would shed some LOCs, and
> the WiFi stack could get set-associativity...
I'm totally not sold on the need for set-associativity. Recently
though, I started thinking about doing dynamic minimal perfect
hashing, as most ip addresses (and for that matter, mac addresses) are
pretty long term stable. If we can calculate a minimal perfect hash
(see cmph for example) fairly rapidly set associativity goes away...
(but I don't have huge hopes for it as yet)
I'm also impressed with the early analysis of cobalt's AQM implementation.
I would like very much, however, for a close look at how much
ack-filtering would benefit wifi.
and funding for next year is on my mind. Not sure how to wedge
anything into nl.net's RFP, but...
And then there's the class-e stuff
busy, busy, busy. Fixing the internet never ends!
>
> -Toke
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
prev parent reply other threads:[~2018-12-11 20:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 22:27 Dave Taht
2018-12-06 7:50 ` Toke Høiland-Jørgensen
2018-12-06 20:03 ` Dave Taht
2018-12-06 19:13 ` David Lang
2018-12-06 20:21 ` Dave Taht
2018-12-11 18:32 ` Aaron Wood
2018-12-11 18:37 ` Dave Taht
2018-12-11 18:38 ` Dave Taht
2018-12-11 18:38 ` Jonathan Morton
2018-12-11 18:39 ` Dave Taht
2018-12-11 20:23 ` Toke Høiland-Jørgensen
2018-12-11 20:35 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5YJsDxJod5yKYTA8h1yPqFbxxcVuuDj5WuD-njSbaAFA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=toke@toke.dk \
--cc=woody77@gmail.com \
/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