From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
codel@lists.bufferbloat.net
Subject: [LibreQoS] QDISC_DROP_REASON project
Date: Fri, 28 Oct 2022 13:34:54 -0700 [thread overview]
Message-ID: <CAA93jw4cRh6MQw23=EhYWq3N3QKn+_QFk8=2RwWhhr0Xd9cYUA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw57yAkTQTTZBhNuk8Ft-iHzNiaaZhuBN-BQ=TFu17dvbg@mail.gmail.com>
There were, at last count, 2600+ places where packets could be dropped
in the linux kernel, and that doesn't account for just dropping
packets at the physical layer and (I don't think) on the rx ring.
DROP_REASON support has been migrating into the kernel, but not yet
for qdiscs, and were it there, it would provide a convenient
tracepoint for why it happened, be it congestive, overflow, or self
defense.
You can pull apart the packets and see where they were going or where
they came from, and so on.
And it's kind of bad to be dropping packets for any other reason,
elsewhere in the system.
Similarly I am seeing a LOT of ecn marking in the field that I am not
sure is correct or not, and there's not a good way to track that
presently.
I had a student lined up for this, but she dropped out. I'd much
rather teach someone how to do this pretty basic job inside the kernel
than do it myself, so if you know anyone with even modest kernel
skills willing to take it on with me, I'd appreciate it.
- https://github.com/rchac/LibreQoS/issues/143
On Fri, Oct 28, 2022 at 1:12 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> There is a ton of grant money going around, and various funds are
> closing at the end of this month or the next. If you know talented
> people that are being laid off, or just want to practice their craft
> in any way to make for a better internet, please pass these links
> along. If you know of any other funding sources, please post? I'd like
> to get a stable floor back under make-wifi-fast in particular, and
> find folk willing to fund or help out (and test) on the libreqos.io
> project.
>
> NLNET is eu only and has two funds focused on privacy and security.
> They are typically good for 30-50k eu and run for a year, a very short
> (3 pages or less) application flies well with them. Closing december 1st:
>
> https://nlnet.nl/assure/
> https://nlnet.nl/entrust/
>
> NLNET has been a huge supporter of bufferbloat.net over the years,
> most recently funding my "cerowrt ii" project, which was a
> constructive failure, in that I lost way too much time to dealing with
> regressions in the stack to make the slightest bit of forward
> progress.
>
> In germany there' s this:
>
> https://forum.openwrt.org/t/germanys-sovereign-tech-fund/141089
>
> And in america, ARDC is very focused on wireless applications.
>
> https://www.ampr.org/grants/
>
> The NSF POSE grants program just closed (we didn't qualify), pouring
> 21m into various open source orgs, or so I hope.
>
> --
> 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
--
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
prev parent reply other threads:[~2022-10-28 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 20:12 [LibreQoS] grant funding avail for various open source projects Dave Taht
2022-10-28 20:34 ` 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='CAA93jw4cRh6MQw23=EhYWq3N3QKn+_QFk8=2RwWhhr0Xd9cYUA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=starlink@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