From: Zvi Effron <zeffron@riotgames.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Zvi Effron <zeffron@riotgames.com>
Subject: [PATCH bpf-next 0/3] bpf: support input xdp_md context in BPF_PROG_TEST_RUN
Date: Mon, 24 May 2021 22:05:52 +0000 [thread overview]
Message-ID: <20210524220555.251473-1-zeffron@riotgames.com> (raw)
This patchset add support for passing a xdp_md via ctx_in/ctx_out in bpf_attr
for BPF_PROG_TEST_RUN of XDP programs.
Patch 1 adds initial support for passing XDP meta data in addition to packet
data.
Patch 2 adds support for also specifying the ingress interface and rx queue.
Patch 3 adds selftests to ensure functionality is correct.
Zvi Effron (3):
bpf: support input xdp_md context in BPF_PROG_TEST_RUN
bpf: support specifying ingress via xdp_md context in
BPF_PROG_TEST_RUN
selftests/bpf: Add test for xdp_md context in BPF_PROG_TEST_RUN
include/uapi/linux/bpf.h | 3 -
net/bpf/test_run.c | 92 +++++++++++++-
.../bpf/prog_tests/xdp_context_test_run.c | 117 ++++++++++++++++++
.../bpf/progs/test_xdp_context_test_run.c | 22 ++++
4 files changed, 225 insertions(+), 9 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/xdp_context_test_run.c
create mode 100644 tools/testing/selftests/bpf/progs/test_xdp_context_test_run.c
base-commit: f9bceaa59c5c47a8a08f48e19cbe887e500a1978
--
2.31.1
next reply other threads:[~2021-05-24 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 22:05 Zvi Effron [this message]
2021-05-24 22:05 ` [PATCH bpf-next 1/3] bpf: support input xdp_md context in BPF_PROG_TEST_RUN Zvi Effron
2021-05-24 22:05 ` [PATCH bpf-next 2/3] bpf: support specifying ingress via " Zvi Effron
2021-05-24 22:05 ` [PATCH bpf-next 3/3] selftests/bpf: Add test for " Zvi Effron
2021-05-26 21:05 ` Andrii Nakryiko
2021-05-26 12:40 ` [PATCH bpf-next 0/3] bpf: support input " Daniel Borkmann
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=20210524220555.251473-1-zeffron@riotgames.com \
--to=zeffron@riotgames.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.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).