From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: John Fastabend <john.fastabend@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org
Subject: Re: [bpf-next PATCH v2 3/3] bpf: selftest additions for SOCKHASH
Date: Fri, 27 Apr 2018 17:10:40 -0700 [thread overview]
Message-ID: <20180428001039.prfomdptje6ywn3k@ast-mbp> (raw)
In-Reply-To: <20180427232443.9985.48093.stgit@john-Precision-Tower-5810>
On Fri, Apr 27, 2018 at 04:24:43PM -0700, John Fastabend wrote:
> This runs existing SOCKMAP tests with SOCKHASH map type. To do this
> we push programs into include file and build two BPF programs. One
> for SOCKHASH and one for SOCKMAP.
>
> We then run the entire test suite with each type.
>
> Signed-off-by: John Fastabend <john.fastabend@gmail.com>
> ---
> tools/testing/selftests/bpf/Makefile | 3
> tools/testing/selftests/bpf/test_sockhash_kern.c | 4
> tools/testing/selftests/bpf/test_sockmap.c | 27 +-
> tools/testing/selftests/bpf/test_sockmap_kern.c | 340 ----------------------
> tools/testing/selftests/bpf/test_sockmap_kern.h | 340 ++++++++++++++++++++++
> 5 files changed, 368 insertions(+), 346 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/test_sockhash_kern.c
> create mode 100644 tools/testing/selftests/bpf/test_sockmap_kern.h
Looks like it was mainly a rename of test_sockmap_kern.c into .h
but commit doesn't show it as such.
Can you redo it with 'git mv' ?
next prev parent reply other threads:[~2018-04-28 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 23:24 [bpf-next PATCH v2 0/3] Hash support for sock John Fastabend
2018-04-27 23:24 ` [bpf-next PATCH v2 1/3] bpf: sockmap, refactor sockmap routines to work with hashmap John Fastabend
2018-04-27 23:24 ` [bpf-next PATCH v2 2/3] bpf: sockmap, add hash map support John Fastabend
2018-04-28 0:09 ` Alexei Starovoitov
2018-04-27 23:24 ` [bpf-next PATCH v2 3/3] bpf: selftest additions for SOCKHASH John Fastabend
2018-04-28 0:10 ` Alexei Starovoitov [this message]
2018-04-29 3:43 ` John Fastabend
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=20180428001039.prfomdptje6ywn3k@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--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