From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/2] minor bpf improvements
Date: Sun, 19 Oct 2025 09:59:45 -0700 [thread overview]
Message-ID: <20251019170040.166372-1-stephen@networkplumber.org> (raw)
Minor update to BPF. Add allocation annotation and remove VLA.
Stephen Hemminger (2):
bpf: add allocation annotations to functions
bpf: remove dependency on vla
lib/bpf/bpf_pkt.c | 16 +++++++++-------
lib/bpf/meson.build | 2 --
lib/bpf/rte_bpf.h | 11 ++++++++---
3 files changed, 17 insertions(+), 12 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-19 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 16:59 Stephen Hemminger [this message]
2025-10-19 16:59 ` [PATCH 1/2] bpf: add allocation annotations to functions Stephen Hemminger
2025-10-19 16:59 ` [PATCH 2/2] bpf: remove dependency on vla Stephen Hemminger
2025-10-19 20:39 ` [PATCH v2 0/2] minor bpf improvements Stephen Hemminger
2025-10-19 20:39 ` [PATCH v2 1/2] bpf: add allocation annotations to functions Stephen Hemminger
2025-10-19 20:39 ` [PATCH v2 2/2] bpf: remove dependency on vla 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=20251019170040.166372-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).