public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Wythe" <alibuda@linux.alibaba.com    >
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: "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,
	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, kuba@kernel.org, davem@davemloft.net,
	netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-rdma@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 5/5] bpf/selftests: add selftest for bpf_smc_ops
Date: Wed, 22 Jan 2025 09:51:09 +0800	[thread overview]
Message-ID: <20250122015109.GA11751@j66a10360.sqa.eu95> (raw)
In-Reply-To: <0d398524-f335-4346-902d-7d7cd3b0685b@linux.dev>

On Fri, Jan 17, 2025 at 04:37:04PM -0800, Martin KaFai Lau wrote:
> On 1/15/25 11:44 PM, D. Wythe wrote:
> >This tests introduces a tiny smc_ops for filtering SMC connections based on
> >IP pairs, and also adds a realistic topology model to verify this ops.
> >
> >Also, we can only use SMC loopback under CI test, so an
> >additional configuration needs to be enabled.
> >
> >Follow the steps below to run this test.
> >
> >make -C tools/testing/selftests/bpf
> >cd tools/testing/selftests/bpf
> >sudo ./test_progs -t smc
> >
> >Results shows:
> >Summary: 1/1 PASSED, 0 SKIPPED, 0 FAILED
> >
> >Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
> >---
> >  tools/testing/selftests/bpf/config            |   4 +
> >  .../selftests/bpf/prog_tests/test_bpf_smc.c   | 397 ++++++++++++++++++
> >  tools/testing/selftests/bpf/progs/bpf_smc.c   | 117 ++++++
> >  3 files changed, 518 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/config b/tools/testing/selftests/bpf/config
> >index c378d5d07e02..fac2f2a9d02f 100644
> >--- a/tools/testing/selftests/bpf/config
> >+++ b/tools/testing/selftests/bpf/config
> >@@ -113,3 +113,7 @@ CONFIG_XDP_SOCKETS=y
> >  CONFIG_XFRM_INTERFACE=y
> >  CONFIG_TCP_CONG_DCTCP=y
> >  CONFIG_TCP_CONG_BBR=y
> >+CONFIG_INFINIBAND=y
> >+CONFIG_SMC=y
> >+CONFIG_SMC_OPS=y
> >+CONFIG_SMC_LO=y
> >\ No newline at end of file
> >+	int fd, ret;
> >+	pid_t pid;
> >+
> >+	fd = socket(AF_NETLINK, SOCK_RAW, NETLINK_GENERIC);
> >+	if (!ASSERT_GT(fd, 0, "nl_family socket"))
> 
> Should be _GE. or just use ASSERT_OK_FD.
> 
Take it.
> >+	if (!ASSERT_GE(ret, 0, "nl_family bind"))
> 
> nit. ASSERT_OK.
> 
> >+	if (!ASSERT_EQ(ret, 0, "nl_family query"))
> 
> ASSERT_OK.
> 
> >+	if (!ASSERT_GT(fd, 0, "ueid socket"))
> 
> ASSERT_OK_FD
> 
> >+		return false;
> >+	ret = bind(fd, (struct sockaddr *) &nl_src, sizeof(nl_src));
> >+	if (!ASSERT_GE(ret, 0, "ueid bind"))
> 
> ASSERT_OK
> 
> >+		goto fail;
> >+	ret = send_cmd(fd, smc_nl_family_id, pid,
> >+		       (void *)test_ueid, sizeof(test_ueid));
> >+	if (!ASSERT_EQ(ret, 0, "ueid cmd"))
> 
> ASSERT_OK
> 

The parts of the assert macro have been all fixed, thanks for your
suggestion.

> >+		goto fail;
> >+
> >+int BPF_PROG(bpf_smc_switch_to_fallback, struct smc_sock___local *smc)
> >+{
> >+	/* only count from one side (client) */
> >+	if (smc && !BPF_CORE_READ(smc, listen_smc))
> 
> It should not need BPF_CORE_READ. smc can be directly read like the
> above sock->sk->...

Got it. I'll fix it in next version.

Thanks,
D. Wythe

> 
> >+		fallback_cnt++;
> >+	return 0;
> >+}

  reply	other threads:[~2025-01-22  1:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  7:44 [PATCH bpf-next v6 0/5] net/smc: Introduce smc_ops D. Wythe
2025-01-16  7:44 ` [PATCH bpf-next v6 1/5] bpf: export necessary sympols for modules with struct_ops D. Wythe
2025-01-16  7:44 ` [PATCH bpf-next v6 2/5] net/smc: Introduce generic hook smc_ops D. Wythe
2025-01-16 12:22   ` Dust Li
2025-01-17 23:50   ` Martin KaFai Lau
2025-01-22  4:35     ` D. Wythe
2025-01-16  7:44 ` [PATCH bpf-next v6 3/5] net/smc: bpf: register smc_ops info struct_ops D. Wythe
2025-01-16  7:44 ` [PATCH bpf-next v6 4/5] libbpf: fix error when st-prefix_ops and ops from differ btf D. Wythe
2025-01-17 18:36   ` Andrii Nakryiko
2025-01-22  2:43     ` D. Wythe
2025-01-22 17:16       ` Andrii Nakryiko
2025-01-16  7:44 ` [PATCH bpf-next v6 5/5] bpf/selftests: add selftest for bpf_smc_ops D. Wythe
2025-01-18  0:37   ` Martin KaFai Lau
2025-01-22  1:51     ` D. Wythe [this message]
2025-01-21  6:42   ` Saket Kumar Bhaskar
2025-01-22  2:46     ` D. Wythe
2025-01-22  4:39       ` Saket Kumar Bhaskar

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=20250122015109.GA11751@j66a10360.sqa.eu95 \
    --to=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=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