From: John Fastabend <john.fastabend@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net
Cc: netdev@vger.kernel.org
Subject: [bpf-next PATCH 0/4] selftests for BPF sockmap use cases
Date: Mon, 23 Apr 2018 14:30:23 -0700 [thread overview]
Message-ID: <20180423212506.20332.6762.stgit@john-Precision-Tower-5810> (raw)
This series moves ./samples/sockmap into BPF selftests. There are a
few good reasons to do this. First, by pushing this into selftests
the tests will be run automatically. Second, sockmap was not really
a sample of anything anymore, but rather a large set of tests.
Note: There are three recent fixes outstanding against bpf branch
that can be detected occosionally by the automated tests here.
https://patchwork.ozlabs.org/patch/903138/
https://patchwork.ozlabs.org/patch/903139/
https://patchwork.ozlabs.org/patch/903140/
---
John Fastabend (4):
bpf: sockmap, code sockmap_test in C
bpf: sockmap, add a set of tests to run by default
bpf: sockmap, add selftests
bpf: sockmap, remove samples program
samples/sockmap/Makefile | 75 -
samples/sockmap/sockmap_kern.c | 341 -----
samples/sockmap/sockmap_test.sh | 488 --------
samples/sockmap/sockmap_user.c | 894 --------------
tools/include/uapi/linux/bpf.h | 1
tools/include/uapi/linux/if_link.h | 39 +
tools/lib/bpf/libbpf.c | 4
tools/lib/bpf/libbpf.h | 2
tools/testing/selftests/bpf/Makefile | 5
tools/testing/selftests/bpf/test_sockmap.c | 1465 +++++++++++++++++++++++
tools/testing/selftests/bpf/test_sockmap_kern.c | 340 +++++
11 files changed, 1852 insertions(+), 1802 deletions(-)
delete mode 100644 samples/sockmap/Makefile
delete mode 100644 samples/sockmap/sockmap_kern.c
delete mode 100755 samples/sockmap/sockmap_test.sh
delete mode 100644 samples/sockmap/sockmap_user.c
create mode 100644 tools/testing/selftests/bpf/test_sockmap.c
create mode 100644 tools/testing/selftests/bpf/test_sockmap_kern.c
next reply other threads:[~2018-04-23 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 21:30 John Fastabend [this message]
2018-04-23 21:30 ` [bpf-next PATCH 1/4] bpf: sockmap, code sockmap_test in C John Fastabend
2018-04-23 21:30 ` [bpf-next PATCH 2/4] bpf: sockmap, add a set of tests to run by default John Fastabend
2018-04-23 21:30 ` [bpf-next PATCH 3/4] bpf: sockmap, add selftests John Fastabend
2018-04-23 21:30 ` [bpf-next PATCH 4/4] bpf: sockmap, remove samples program John Fastabend
2018-04-24 22:22 ` [bpf-next PATCH 0/4] selftests for BPF sockmap use cases 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=20180423212506.20332.6762.stgit@john-Precision-Tower-5810 \
--to=john.fastabend@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.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