From: Stephen Hemminger <stephen@networkplumber.org>
To: Stefan Alfredsson <stefan.alfredsson@kau.se>
Cc: <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] vyatta in AT&T 5G gear
Date: Tue, 16 Oct 2018 08:06:28 -0700 [thread overview]
Message-ID: <20181016080628.2ca3652b@xeon-e3> (raw)
In-Reply-To: <68031ed5-05e5-8f53-5e7d-ef0fce9d08da@kau.se>
On Tue, 16 Oct 2018 11:59:18 +0200
Stefan Alfredsson <stefan.alfredsson@kau.se> wrote:
> On 2018-10-16 11:31, Mikael Abrahamsson wrote:
>
> > On Mon, 15 Oct 2018, Dave Taht wrote:
> >
> >> Vyos (the open source fork of vyatta) was one of the first to add
> >> fq_codel support... I wonder....
> >>
> >> http://linuxgizmos.com/att-releases-white-box-spec-for-its-linux-based-5g-routers/
> >>
> >
> > Isn't Vyos just running the Linux kernel for forwarding? So they
> > received fq_codel for free when the Linux kernel got support for it?
> > They just had to make it configurable?
> >
>
> Yes, according to this blog post,
> http://www.five-ten-sg.com/mapper/blog/Bufferbloat%20solved%20with%20Vyos
>
> "Now that Vyos "helium" is available with a Linux 3.13 kernel, the
> fq_codel queueing discipline can be used to solve many bufferbloat
> issues. The nightly "lithium" builds contain my patches that allow
> fq_codel to be used via the native Vyos configuration system."
>
> Anyway it's nice to see the Vyatta heritage living on in it's various
> forms (the AT&T "production hardened" Vyatta, to the Ubiquity EdgeMax
> and some UniFi devices, to the VyOS open version and now the future
> plans with dNOS -> DANOS.
>
> /Stefan
>
>
>
There are two basic components to network OS, the control plane and the
data plane. VyOs has the old V1 which is filesystem based control plane
and kernel dataplane. DaNoS has yang/netconf database based control plane
(in Go) and DPDK (or switch offload?) based dataplane. Ubiquity redid
the control plane as well, and uses their own hardware for dataplane.
So more of "my grandfather's ax"...
next prev parent reply other threads:[~2018-10-16 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 3:07 Dave Taht
2018-10-16 9:31 ` Mikael Abrahamsson
2018-10-16 9:59 ` Stefan Alfredsson
2018-10-16 15:06 ` Stephen Hemminger [this message]
2018-10-16 15:14 ` Dave Taht
2018-10-16 15:26 ` Jan Ceuleers
2018-10-17 0:46 ` Dave Taht
2018-10-18 19:45 ` Stephen Hemminger
2018-10-16 15:57 ` Stephen Hemminger
2018-10-21 9:36 ` Jonas Mårtensson
2018-10-22 16:42 ` Stephen Hemminger
2018-10-22 17:00 ` Dave Taht
2018-10-22 20:45 ` Toke Høiland-Jørgensen
2018-10-23 7:38 ` Jonas Mårtensson
2018-10-23 15:27 ` Stephen Hemminger
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181016080628.2ca3652b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=stefan.alfredsson@kau.se \
/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