From: Herbert Wolverson <herberticus@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] milestone madness
Date: Mon, 14 Nov 2022 10:45:05 -0600 [thread overview]
Message-ID: <CA+erpM5efECeo7aHzd1vbXsg-ES7_VPiP8DPj-RqEE6pTRxJ3A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw621Yt1asiTY8phngnRWWjDF9aMgtKyo2cx5MUNMm=bOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1799 bytes --]
Hopefully, I'll have the xdp_pping issue nailed down and cpumap-pping up to
1.0 shortly.
Context:
We ran into an issue in which the userspace xdp_pping program would sit and
spin at 100%
CPU load (on a single core) with traffic around 5 gbit/s. So I'm testing a
fix, the relevant issue
is here: https://github.com/thebracket/cpumap-pping/issues/4
On Sun, Nov 13, 2022 at 11:58 AM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> after YEARS of me b*tching about how github's bug tracker was inferior
> to bugzilla and redmine and presented nothing but a swamp of
> unproritized unreadable messes of bugs, I finally sat down today to
> bend it to my will...
>
> ... and won! (mostly)
>
> I apologize for the sea of emails y'all got while wrestling it into
> shape. It was REALLY great to see all the bugs that had been closed
> on the march to the 1.3 release, and a relief to punt a zillion other
> bugs to the v1.4 release, and now if y'all could review and comment on
> these few remaining bugs, I'd love to freeze the code on nov 15th as
> planned and proceed with the beta.
>
>
> https://github.com/LibreQoE/LibreQoS/issues?q=is%3Aissue+is%3Aopen+milestone%3Av1.3
>
> If there's something you wanted that I punted, see here:
>
>
> https://github.com/LibreQoE/LibreQoS/issues?q=is%3Aissue+is%3Aopen+milestone%3Av1.4
>
> Thank you all for your help and participation!
>
> --
> 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: 2868 bytes --]
prev parent reply other threads:[~2022-11-14 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 17:58 Dave Taht
2022-11-14 16:45 ` 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+erpM5efECeo7aHzd1vbXsg-ES7_VPiP8DPj-RqEE6pTRxJ3A@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