General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Luca Muscariello <luca.muscariello@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] occasionally, there's good news to be had for the Internet.
Date: Mon, 12 Feb 2018 10:25:09 +0100	[thread overview]
Message-ID: <CAHx=1M5McnUebhx_5AE9-vMsf66eYe9WUr5dWfyBBVD1Ruv+iw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4AF1wvSokvjvvfU8q8pSAhtJxGkMEodvXCxFb7V-NwOA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

Next challenge: FQ into silicon...

One of the reasons of what Jim describes under the "Here lies madness"
section
is related to silicon built-in functionalities and the ability to update
software in edge-routers.

Many chipcos build their board with several  CPU offloading mechanisms,
e.g.
to support 1Gbps in the home.

My home router uses a fourth-generation BCM3384 euro-DOCSIS 3.0
System-on-a-Chip (SoC)
capable of 1Gbps downstream speeds by bonding up to 24x8 DOCSIS channels.
One at 600MHz for the modem and one for the OS at 1GHz.

I get 1Gbps downstream reliably and excessive latency too, ...reliably.

It's a Linux box in the end but no way to enable FQ_codel based on the
current architecture
as TCP pipelines are offloaded to silicon.

the are all sort of acceleration in the SoC, so I don't see it impossible
to get FQ there.



On Mon, Feb 12, 2018 at 9:31 AM, Dave Taht <dave.taht@gmail.com> wrote:

> I wish that more people agreed that fair queuing and AQM were the
> rightest answers to the political debate, of both sides, to
> NetworkNeutrality. RF8290 is fair to flows, no matter whose they are.
> I also would like stuff like what Jim just wrote to somehow escape the
> filter bubble, compressed down into terms found in everyday language.
> Or a checkbox item on an RFP.
>
> https://gettys.wordpress.com/2018/02/11/the-blind-men-and-the-elephant/
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 2738 bytes --]

      reply	other threads:[~2018-02-12  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12  8:31 Dave Taht
2018-02-12  9:25 ` Luca Muscariello [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/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='CAHx=1M5McnUebhx_5AE9-vMsf66eYe9WUr5dWfyBBVD1Ruv+iw@mail.gmail.com' \
    --to=luca.muscariello@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@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