From: "Aaron A. Glenn" <aag@predictedpaths.nl>
To: "Dave Taht" <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] expandable tofino... so how far as p4 come?
Date: Sat, 26 Nov 2022 06:31:14 +0000 [thread overview]
Message-ID: <634d3b81-2090-4200-a2ac-776c47e66553@app.fastmail.com> (raw)
In-Reply-To: <CAA93jw4wRPEbkTOYipkBhepMu9DcVM68T0SWw-XvGA+yO0OUgg@mail.gmail.com>
HQoS and 8GB+ packet buffer like the big merchant silicon can do.
slap another one in and you can get 20MM route lookup table memory like big vendor silicon can do, too.
what's "ultra low delay" mean to you/this list?
On Sat, Nov 26, 2022, at 00:54, Dave Taht via LibreQoS wrote:
> enables...
>
> "Telco gateway functions such as Broadband Network Gateway (BNG) and
> the Access Gateway Function (AGF), which require extra-large buffers
> for advanced hierarchical traffic shaping, scheduling, and policing
> for fixed network and 5G residential gateways" -
> https://medium.com/intel-tech/intel-tofino-expandable-architecture-paves-way-for-advanced-use-case-multi-terabit-switches-and-80b42c02e730
>
> What does extra large mean?
>
> Or ultra-low-delay?
>
> --
> This song goes out to all the folk that thought Stadia would work:
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
--
Aaron A. Glenn,
Managing Director
Predicted Paths BV
Keizersgracht 62-64,
NL-1015 CS Amsterdam
Tel / Fax +31 85 208 2733
NL861040715B01 / KvK 77542223
prev parent reply other threads:[~2022-11-26 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 0:54 Dave Taht
2022-11-26 1:02 ` [LibreQoS] intel BNG kit Dave Taht
2022-11-26 6:31 ` Aaron A. Glenn [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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=634d3b81-2090-4200-a2ac-776c47e66553@app.fastmail.com \
--to=aag@predictedpaths.nl \
--cc=libreqos@lists.bufferbloat.net \
/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