From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: "D. Wythe" <alibuda@linux.alibaba.com>,
kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, pabeni@redhat.com, song@kernel.org,
sdf@google.com, haoluo@google.com, yhs@fb.com,
edumazet@google.com, john.fastabend@gmail.com,
kpsingh@kernel.org, jolsa@kernel.org, guwen@linux.alibaba.com
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
bpf@vger.kernel.org, dtcccc@linux.alibaba.com
Subject: Re: [PATCH bpf-next 4/4] bpf/selftests: add simple selftest for bpf_smc_ops
Date: Sun, 3 Nov 2024 14:01:35 +0100 [thread overview]
Message-ID: <8c06240b-540b-472f-974f-d2db80d90c22@linux.dev> (raw)
In-Reply-To: <1729737768-124596-5-git-send-email-alibuda@linux.alibaba.com>
在 2024/10/24 4:42, D. Wythe 写道:
> From: "D. Wythe" <alibuda@linux.alibaba.com>
>
> This PATCH adds a tiny selftest for bpf_smc_ops, to verify the ability
> to attach and write access.
>
> Follow the steps below to run this test.
>
> make -C tools/testing/selftests/bpf
> cd tools/testing/selftests/bpf
> sudo ./test_progs -t smc
Thanks a lot.
# ./test_progs -t smc
#27/1 bpf_smc/load:OK
#27 bpf_smc:OK
Summary: 1/1 PASSED, 0 SKIPPED, 0 FAILED
The above command is based on several kernel modules. After these
dependent kernel modules are loaded, then can run the above command
successfully.
Zhu Yanjun
>
> Results shows:
> Summary: 1/1 PASSED, 0 SKIPPED, 0 FAILED
>
> Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
> ---
> .../selftests/bpf/prog_tests/test_bpf_smc.c | 21 +++++++++++
> tools/testing/selftests/bpf/progs/bpf_smc.c | 44 ++++++++++++++++++++++
> 2 files changed, 65 insertions(+)
> create mode 100644 tools/testing/selftests/bpf/prog_tests/test_bpf_smc.c
> create mode 100644 tools/testing/selftests/bpf/progs/bpf_smc.c
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/test_bpf_smc.c b/tools/testing/selftests/bpf/prog_tests/test_bpf_smc.c
> new file mode 100644
> index 00000000..2299853
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/prog_tests/test_bpf_smc.c
> @@ -0,0 +1,21 @@
> +// SPDX-License-Identifier: GPL-2.0
> +#include <test_progs.h>
> +
> +#include "bpf_smc.skel.h"
> +
> +static void load(void)
> +{
> + struct bpf_smc *skel;
> +
> + skel = bpf_smc__open_and_load();
> + if (!ASSERT_OK_PTR(skel, "bpf_smc__open_and_load"))
> + return;
> +
> + bpf_smc__destroy(skel);
> +}
> +
> +void test_bpf_smc(void)
> +{
> + if (test__start_subtest("load"))
> + load();
> +}
> diff --git a/tools/testing/selftests/bpf/progs/bpf_smc.c b/tools/testing/selftests/bpf/progs/bpf_smc.c
> new file mode 100644
> index 00000000..ebff477
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/progs/bpf_smc.c
> @@ -0,0 +1,44 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +#include "vmlinux.h"
> +
> +#include <bpf/bpf_helpers.h>
> +#include <bpf/bpf_tracing.h>
> +
> +char _license[] SEC("license") = "GPL";
> +
> +struct smc_bpf_ops_ctx {
> + struct {
> + struct tcp_sock *tp;
> + } set_option;
> + struct {
> + const struct tcp_sock *tp;
> + struct inet_request_sock *ireq;
> + int smc_ok;
> + } set_option_cond;
> +};
> +
> +struct smc_bpf_ops {
> + void (*set_option)(struct smc_bpf_ops_ctx *ctx);
> + void (*set_option_cond)(struct smc_bpf_ops_ctx *ctx);
> +};
> +
> +SEC("struct_ops/bpf_smc_set_tcp_option_cond")
> +void BPF_PROG(bpf_smc_set_tcp_option_cond, struct smc_bpf_ops_ctx *arg)
> +{
> + arg->set_option_cond.smc_ok = 1;
> +}
> +
> +SEC("struct_ops/bpf_smc_set_tcp_option")
> +void BPF_PROG(bpf_smc_set_tcp_option, struct smc_bpf_ops_ctx *arg)
> +{
> + struct tcp_sock *tp = arg->set_option.tp;
> +
> + tp->syn_smc = 1;
> +}
> +
> +SEC(".struct_ops.link")
> +struct smc_bpf_ops sample_smc_bpf_ops = {
> + .set_option = (void *) bpf_smc_set_tcp_option,
> + .set_option_cond = (void *) bpf_smc_set_tcp_option_cond,
> +};
next prev parent reply other threads:[~2024-11-03 13:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 2:42 [PATCH bpf-next 0/4] net/smc: Introduce smc_bpf_ops D. Wythe
2024-10-24 2:42 ` [PATCH bpf-next 1/4] bpf: export necessary sympols for modules D. Wythe
2024-10-24 2:42 ` [PATCH bpf-next 2/4] bpf: allow to access bpf_prog during bpf_struct_access D. Wythe
2024-10-25 9:14 ` kernel test robot
2024-10-25 12:20 ` kernel test robot
2024-10-24 2:42 ` [PATCH net-next 3/4] net/smc: Introduce smc_bpf_ops D. Wythe
2024-10-25 0:26 ` Martin KaFai Lau
2024-10-25 11:05 ` D. Wythe
2024-10-25 18:30 ` Martin KaFai Lau
2024-10-29 8:53 ` D. Wythe
2024-10-24 2:42 ` [PATCH bpf-next 4/4] bpf/selftests: add simple selftest for bpf_smc_ops D. Wythe
2024-10-24 4:04 ` D. Wythe
2024-10-24 4:49 ` Tianchen Ding
2024-10-24 5:49 ` D. Wythe
2024-11-03 13:01 ` Zhu Yanjun [this message]
2024-11-21 2:00 ` D. Wythe
2024-11-25 10:52 ` Zhu Yanjun
2024-11-25 23:32 ` Martin KaFai Lau
2024-11-26 8:29 ` Zhu Yanjun
2024-11-29 4:11 ` D. Wythe
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=8c06240b-540b-472f-974f-d2db80d90c22@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dtcccc@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=jaka@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kgraul@linux.ibm.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=wenjia@linux.ibm.com \
--cc=yhs@fb.com \
/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