From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>
Cc: Tom Herbert <tom@herbertland.com>
Subject: [Make-wifi-fast] the panda flow-dissector
Date: Sun, 24 Oct 2021 09:24:30 -0700 [thread overview]
Message-ID: <CAA93jw4hb7NgkHQrV=nVsg=4DevBewLQLnTE6S-aUjXaHtzY_A@mail.gmail.com> (raw)
The flow-dissector in linux is the unsung hero of our fq+aqm world.
It's also heavily used for receive packet steering (to shift a flow to
another core) and in tc-flower, and can deeply inspect a packet to
find the real 5 tuple, among other things. We are very used to, in the
linux world, to having that hash always available.
So far as I know BSD's equivalent is considerably weaker, as are the
offloads people are attempting in p4, and in qualcomm's nss hardware
offloads. Anyway, as it is large, and fragile code,
there is now a (bsd 2-clause) panda packet parser generator over here:
https://github.com/panda-net/panda
... that could possibly be retargetted at those environments as well
as one day replace and unify the existing flow dissector codes.
Tom Herbert talks to it in detail here. See the spaghetti for why this
is needed in more places.
https://www.youtube.com/watch?v=zVnmVDSEoXc
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2021-10-24 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4hb7NgkHQrV=nVsg=4DevBewLQLnTE6S-aUjXaHtzY_A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=tom@herbertland.com \
/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