From: Dave Taht <dave.taht@gmail.com>
To: Frank Carmickle <frank@carmickle.com>
Cc: 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 09:30:00 -0600 [thread overview]
Message-ID: <CAA93jw6VM37YQa5MhC_8OeDonMqRerfSYE7uyYSAE2gX4imkCA@mail.gmail.com> (raw)
In-Reply-To: <61385F96-B1B4-4FED-A035-7932905D30C4@carmickle.com>
The simplest possible thing is SFP on an OLT that actually sends
ethernet pause frames when the local buffer has enough data, which
so far as I can tell from looking at GPON specs is about 250us . That
would let a router on the other side of it, just run good ole fq_codel
+ BQL without needing any shaping there. That exist?
prev parent reply other threads:[~2023-07-11 15:30 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
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 [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=CAA93jw6VM37YQa5MhC_8OeDonMqRerfSYE7uyYSAE2gX4imkCA@mail.gmail.com \
--to=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