From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
"Richard E. Brown" <richb.hanover@gmail.com>
Subject: Re: [Cake] vyos w/fq_codel and cake
Date: Wed, 11 Oct 2023 09:49:59 -0700 [thread overview]
Message-ID: <20231011094959.59b6d9e0@hermes.local> (raw)
In-Reply-To: <CAA93jw4YrKZJR7JDGg8hCRHO+t4KU4Txd0phWsu+v_5cCwFXKQ@mail.gmail.com>
On Wed, 11 Oct 2023 08:26:17 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> After successfully having got them to switch the default over to
> fq_codel last week,
> I started looking over their very old skool traffic shaping policies.
> Does anyone here use vyos? I used to really like it, but kind of went
> pure openwrt, and now very little at all.
>
> https://forum.vyos.io/t/qos-qoe-support-in-vyos/12376/2
>
> https://docs.vyos.io/en/latest/configuration/trafficpolicy/index.html
>
>
They forked from old Vyatta long ago, and have been making good progress.
There were things that we had to do internally: replace CLI processor,
switch routing protocol backend, and stop using kernel for dataplane.
VyOs gradually has done all of those. Last I saw they were switching
over to FD.io/VPP for dataplane. VPP is an all userspace dataplane that
borrows from DPDK.
prev parent reply other threads:[~2023-10-11 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 15:26 Dave Taht
2023-10-11 16:49 ` Stephen Hemminger [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/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=20231011094959.59b6d9e0@hermes.local \
--to=stephen@networkplumber.org \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=richb.hanover@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