From: Herbert Wolverson <herberticus@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] 2/2/23 meeting notes
Date: Thu, 2 Feb 2023 17:35:20 -0600 [thread overview]
Message-ID: <CA+erpM77NNQL_8ppN5E+cdz4z1hQ5J+wwpwFMXUCbJzG_n6rCg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6Wd5eBmJHy=RqaTMoCygxmB=+r3VaorrTc-c6OCwEsLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
Sorry I had to bail, daycare time is a hard cutoff for me.
One thing I forgot to mention is that bracket qos currently stores
historical data for circuits as a whole, not individual IPs - and I hate
that. It's so useful to see a stacked display that tells you which device
(even individual with ipv6) ate your bandwidth.
I also forgot to mention that I love the pixel per queue idea. It makes me
want to integrate WASM even more (that would be one way to avoid more
JavaScript...)
Thanks!
On Thu, Feb 2, 2023, 5:15 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> Are available here:
>
> https://docs.google.com/document/d/1RRQmQFwVada3-OusUE7vlohmMmkAD8tVKfXAVw_QfW0/edit#
>
> they are of course, mildly fragmentary and incomplete. If you have
> questions or comments, please comment on the document not in email,
> please!
>
> thank you everyone for coming!
>
> --
> 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
>
[-- Attachment #2: Type: text/html, Size: 2189 bytes --]
prev parent reply other threads:[~2023-02-02 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 23:15 Dave Taht
2023-02-02 23:35 ` Herbert Wolverson [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=CA+erpM77NNQL_8ppN5E+cdz4z1hQ5J+wwpwFMXUCbJzG_n6rCg@mail.gmail.com \
--to=herberticus@gmail.com \
--cc=dave.taht@gmail.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