From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] Fwd: [NetDev-People] 0x15: New Talk accepted!
Date: Thu, 1 Jul 2021 08:59:29 -0700 [thread overview]
Message-ID: <CAA93jw5VKXrwDwtyN_H6Db_hb815SKQSnVKN5Sx=5V-OSudEzA@mail.gmail.com> (raw)
In-Reply-To: <4705bae2.AVMAADUSX7YAAAAAAAAAAG3K_mQAAYCsBU0AAAAAAAwWzABg3dV1@mailjet.com>
---------- Forwarded message ---------
From: Jamal Hadi Salim via people <people@netdevconf.info>
Date: Thu, Jul 1, 2021 at 7:47 AM
Subject: [NetDev-People] 0x15: New Talk accepted!
To: people <people@netdevconf.info>
Cc: <prog-committee-0x15@netdevconf.info>, <kimberleyjeffries@gmail.com>
Tom Herbert is still on a quest to speed up the network stack[1].
In this talk he introduces the PANDA parser with intention to
replace the venerable Linux kernel Flow Dissector.
Tom says the flow dissector is hard coded, convoluted making
it both hard to extend and hard to maintain.
(yes, he is guilty as well having been one of the originators
of the flow dissector).
PANDA parser is a domain specific parser that lives under
the philosophy of "write once, run anywhere, run well".
Unlike Flow Dissector, a PANDA Parser with metadata extraction
is written in a declarative representation as opposed to imperative
instructions - all in familiar C. It has been shown that while
more flexible, the PANDA parser is more performant than flowdissector.
The PANDA parser may be compiled to different backends, currently
two implemented backends are available: an optimized userspaces C
and an XDP/eBPF one. There is ongoing work on generating a plain
kernel version as well which may be consumed by other part of the
kernel. For any of those 3 backends, the parser definition stays
unchanged.
[1]https://legacy.netdevconf.info/0x14/session.html?talk-BP4-byte-code-for-programmable-protocol-independent-PDU-processing
More info:
https://netdevconf.info/0x15/session.html?Replacing-Flow-Dissector-with-PANDA-Parser
cheers,
jamal
PS: Registration is open, see:
https://netdevconf.info/0x15/registration.html
PPS: We are looking to post the schedule today
_______________________________________________
people mailing list
people@netdevconf.org
https://lists.netdevconf.info/cgi-bin/mailman/listinfo/people
--
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
Dave Täht CTO, TekLibre, LLC
parent reply other threads:[~2021-07-01 15:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4705bae2.AVMAADUSX7YAAAAAAAAAAG3K_mQAAYCsBU0AAAAAAAwWzABg3dV1@mailjet.com>]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5VKXrwDwtyN_H6Db_hb815SKQSnVKN5Sx=5V-OSudEzA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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