From: Pete Heist <pete@heistp.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] customizing Cake's isolation with ipsets, tc-flow and eBPF
Date: Sun, 06 Jun 2021 22:26:42 +0200 [thread overview]
Message-ID: <e29563108ce8841d8c56a428f72bd2644019957a.camel@heistp.net> (raw)
In-Reply-To: <87h7iawyr1.fsf@toke.dk>
On Sun, 2021-06-06 at 21:59 +0200, Toke Høiland-Jørgensen wrote:
> Pete Heist <pete@heistp.net> writes:
>
> > I've always wanted a way to customize Cake's host and flow isolation
> > in
> > a way that would be usable e.g. for small ISPs, and this is what I
> > came
> > up with:
> >
> > https://github.com/heistp/cake-custom-isolation
> >
> > ipsets are used to set the skb priority or mark, then tc-flow or a
> > simple eBPF classifier is used in a child filter of cake to get the
> > major and minor class IDs set, which override the host and flow
> > hashes.
>
> Very cool! Awesome to see the customisation options being used for
> something neat like this! :)
>
> > To show it in action, the cakeiso.sh script sets up a netns
> > environment
> > and runs competition between two "subscribers" and three flows, two
> > TCP
> > flows and one unresponsive UDP flow. Several configurations are run
> > to
> > show what is and isn't possible.
> >
> > If anyone knows of a simpler way than eBPF to get both the major and
> > minor class ID set from ipsets, I'd like to hear it, but the included
> > classifiers are at least very simple one-liners...
>
> Well, you could go the other way? Instead of ipset, just do the
> classification in eBPF and use a BPF map to store the IP addresses.
> There's even an LPM map type, so you can use arbitrary prefix lengths
> for each class (or not, and just use a hashmap)...
True that, I started something like that at some point:
https://github.com/heistp/tc-users/
but I think I got a little overzealous with it. I'm not sure if/when
I'll get back to that, but the ipset solution seems to be "good enough"
for what I (and my ISP) needs. I'm glad you slipped the tc filter
overrides in before Cake went out the door. :)
This doesn't do away with the possible need for a full-blown ISP qdisc
one day, with configurable subscriber tiers, handling of higher loads,
etc, but at least it's something for the little guys.
Pete
> -Toke
next prev parent reply other threads:[~2021-06-06 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 10:11 Pete Heist
2021-06-06 19:59 ` Toke Høiland-Jørgensen
2021-06-06 20:26 ` Pete Heist [this message]
2021-06-06 21:01 ` Toke Høiland-Jørgensen
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=e29563108ce8841d8c56a428f72bd2644019957a.camel@heistp.net \
--to=pete@heistp.net \
--cc=cake@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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