From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC 0/5] BPF infrastructure enhancements
Date: Fri, 5 Jan 2024 14:28:06 -0800 [thread overview]
Message-ID: <20240105222909.139674-1-stephen@networkplumber.org> (raw)
While investigating the BPF program load in TAP device
found a number of minor issues that should be addressed.
Stephen Hemminger (5):
tap: move forward declaration of bpf_load
tap: remove unnecessary bzero() calls in bpf api
tap: remove unnecessary cast in call to bpf_load
tap: get errors from kernel on bpf load failure
tap: stop "vendoring" linux bpf header
drivers/net/tap/bpf/bpf_extract.py | 1 -
drivers/net/tap/tap_bpf.h | 121 -----------------------------
drivers/net/tap/tap_bpf_api.c | 73 +++++++++++------
drivers/net/tap/tap_bpf_insns.h | 1 -
drivers/net/tap/tap_flow.c | 16 ++--
drivers/net/tap/tap_flow.h | 4 +-
6 files changed, 60 insertions(+), 156 deletions(-)
delete mode 100644 drivers/net/tap/tap_bpf.h
--
2.43.0
next reply other threads:[~2024-01-05 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 22:28 Stephen Hemminger [this message]
2024-01-05 22:28 ` [RFC 1/5] tap: move forward declaration of bpf_load Stephen Hemminger
2024-01-05 22:28 ` [RFC 2/5] tap: remove unnecessary bzero() calls in bpf api Stephen Hemminger
2024-01-05 22:28 ` [RFC 3/5] tap: remove unnecessary cast in call to bpf_load Stephen Hemminger
2024-01-05 22:28 ` [RFC 4/5] tap: get errors from kernel on bpf load failure Stephen Hemminger
2024-01-05 22:28 ` [RFC 5/5] tap: stop "vendoring" linux bpf header Stephen Hemminger
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240105222909.139674-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).