From: Jeremy Austin <jeremy@aterlo.com>
To: Frank Carmickle <frank@carmickle.com>
Cc: Dave Taht <dave.taht@gmail.com>,
Dave Taht via LibreQoS <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Got BEAD? Looking for a turnkey partner to help streamline the next steps?
Date: Tue, 11 Jul 2023 07:09:45 -0800 [thread overview]
Message-ID: <CACw=56Jbp0+sEtwuoU8y+N5mJ2-rWHK-K-kTYN9DgmqEkmtOAw@mail.gmail.com> (raw)
In-Reply-To: <6D3D2EAA-88E9-4E0E-8967-AE33853B8F42@carmickle.com>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
On Tue, Jul 11, 2023 at 7:01 AM Frank Carmickle via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> Dave,
>
> > On Jul 11, 2023, at 10:53, Dave Taht via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
> >
> > I know everyone here hates paperwork as much or more than I do.
> >
> > ... but me, in particular, would really like to find an ONT that runs
> fq_codel natively I could recommend.
>
> Have you looked at SFP modules that do PON?
>
> https://www.fs.com/products/141199.html
>
>
> https://community.fs.com/blog/basic-knowledge-about-gpon-sfp-transceivers.html
Can the the thermal envelope for an SFP truly accommodate traffic shaping?
I’m thinking not at the current state of CPU art. Would be delighted to be
wrong.
Jeremy
--
[image: Company logo]
*Jeremy Austin*
Sr. Product Manager
*Preseem | Aterlo Networks*
Book a call: https://app.hubspot.com/meetings/jeremy548
1-833-773-7336 ext 718 <18337737336718> *|* 1-907-803-5422 <19078035422>
jeremy@aterlo.com <email%7D>
www.preseem.com
[image: facebook icon] <https://www.facebook.com/preseem> [image: twitter
icon] <https://twitter.com/preseem> [image: linkedin icon]
<https://www.linkedin.com/company/4287641/> [image: youtube icon]
<https://www.youtube.com/c/Preseem>
[image: Ask us about our new features today!]
<https://preseem.com/features/>
[-- Attachment #2: Type: text/html, Size: 4866 bytes --]
next prev parent reply other threads:[~2023-07-11 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9579202856.3@informz.net>
2023-07-11 14:53 ` [LibreQoS] Fwd: " Dave Taht
2023-07-11 15:01 ` [LibreQoS] " Frank Carmickle
2023-07-11 15:09 ` Jeremy Austin [this message]
2023-07-11 15:13 ` Frank Carmickle
2023-07-11 15:16 ` Jeremy Austin
2023-07-11 15:31 ` Dave Taht
2023-07-11 15:30 ` Dave Taht
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='CACw=56Jbp0+sEtwuoU8y+N5mJ2-rWHK-K-kTYN9DgmqEkmtOAw@mail.gmail.com' \
--to=jeremy@aterlo.com \
--cc=dave.taht@gmail.com \
--cc=frank@carmickle.com \
--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