From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave@taht.net>
Cc: Jan Ceuleers <jan.ceuleers@gmail.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] vyatta in AT&T 5G gear
Date: Thu, 18 Oct 2018 12:45:43 -0700 [thread overview]
Message-ID: <20181018124543.04fc1c35@shemminger-XPS-13-9360> (raw)
In-Reply-To: <87o9bth023.fsf@taht.net>
On Tue, 16 Oct 2018 17:46:44 -0700
Dave Taht <dave@taht.net> wrote:
> Jan Ceuleers <jan.ceuleers@gmail.com> writes:
>
> > On 16/10/2018 17:14, Dave Taht wrote:
> >> And what was so wrong with the "everything as a file" model??
> >
> > On a single box - not a lot.
> >
> > On a 5G network, which might consist of 10^3 - 10^5 boxes you need
> > aggregation and abstraction layers.
>
> I was mostly just venting. Still... I'd hoped that the next generation
> fios gear would get bufferbloat right... and with all the 5G boasting
> about the 1ms mac, that they'd get queuing delay below 20ms also.
>
> I was also hoping the DOCSIS 3.1 line cards would get it right...
>
> It has been a disappointing day.
At scale, you need a usable programming model; on box CLI or files don't work well.
Netconf/yang was built for that.
next prev parent reply other threads:[~2018-10-18 19:45 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
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 [this message]
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=20181018124543.04fc1c35@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=jan.ceuleers@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