From patchwork Wed Dec 18 02:44:16 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "D. Wythe" X-Patchwork-Id: 13912960 Received: from out30-119.freemail.mail.aliyun.com (out30-119.freemail.mail.aliyun.com [115.124.30.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0CE7913F42F; Wed, 18 Dec 2024 02:44:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=115.124.30.119 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734489879; cv=none; b=EbDdZxPcC7BPNWrjiydJXezlSD/dyfcKpe8K8niO0PS1FIyes2EYHLWPSiR9yxHI49tlSMUd35+oxjpTL3zyIfv3tSGlzS1tU9QxJb4bXEEZpBqtrJF+KhrcDGCziRPmSj4FOcWxjc0qFGEy1MUhpREh9Gh3TYMha5/aimEy5/A= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734489879; c=relaxed/simple; bh=AajkgNdYfDVPf5h30MJZ28AMOzbXrlyF3F9tu4DAi9w=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ETdFRXCmQGSrHzEGfAGy2K3dOe9beDk9hktGYun60u8CjquEjPujDIQNo/1YB8kNG7z3pTyI8QciMHTzZW74gaYAaVuXoSPBXS094xsGhjWkDFbbxscqfIZxOdgHnuWrjSwFO8c1+LzAS62RdvUOeANsTqG6BawLjVoKFNlKl4M= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com; spf=pass smtp.mailfrom=linux.alibaba.com; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b=aKI0l9Fs; arc=none smtp.client-ip=115.124.30.119 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b="aKI0l9Fs" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.alibaba.com; s=default; t=1734489868; h=From:To:Subject:Date:Message-ID:MIME-Version; bh=GiaqvJ/ATJVxRZbvIn3hyHmB1fPXH0dg0ZXdH0cIS+k=; b=aKI0l9FsdOz2X4cHeIAnjtDlPFOTQcqu42kLbVEtGvRrBkqXpd9XLMBWJQ9SnH3CajX4bNgTuJjJfNkyxgezvJ94TQZDBIxa+Z7tN2i+Hi/ZU15KgvYb2RwplzBnGXF/ca7myd/pUY8PN4pP5a68z8fBUdwu6dvnV1ieauD5nuI= Received: from j66a10360.sqa.eu95.tbsite.net(mailfrom:alibuda@linux.alibaba.com fp:SMTPD_---0WLko6by_1734489862 cluster:ay36) by smtp.aliyun-inc.com; Wed, 18 Dec 2024 10:44:27 +0800 From: "D. Wythe" To: 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 Subject: [PATCH bpf-next v3 0/5] net/smc: Introduce smc_ops Date: Wed, 18 Dec 2024 10:44:16 +0800 Message-ID: <20241218024422.23423-1-alibuda@linux.alibaba.com> X-Mailer: git-send-email 2.45.0 Precedence: bulk X-Mailing-List: linux-rdma@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 This patches attempt to introduce BPF injection capability for SMC, and add selftest to ensure code stability. Since the SMC protocol is not suitable for all scenarios, especially for short-lived. For most applications, they cannot guarantee that there are no such scenarios at all. Therefore, apps may need some specific strategies to decide shall we need to use SMC or not, for example, apps can limit the scope of the SMC to a specific IP address or port. Based on the consideration of transparent replacement, we hope that apps can remain transparent even if they need to formulate some specific strategies for SMC using. That is, do not need to recompile their code. On the other hand, we need to ensure the scalability of strategies implementation. Although it is simple to use socket options or sysctl, it will bring more complexity to subsequent expansion. Fortunately, BPF can solve these concerns very well, users can write thire own strategies in eBPF to choose whether to use SMC or not. And it's quite easy for them to modify their strategies in the future. v2: 1. Rename smc_bpf_ops to smc_ops. 2. Change the scope of smc_ops from global to per netns. 3. Directly pass parameters to ops instead of smc_ops_ctx. 4. Remove struct smc_ops_ctx. 5. Remove exports that are no longer needed. v3: 1. Remove find_ksym_btf_id_by_prefix_kind. 2. Enhance selftest, introduce a complete ops for filtering smc connections based on ip pairs and a realistic topology test to verify it. D. Wythe (5): bpf: export necessary sympols for modules with struct_ops net/smc: Introduce generic hook smc_ops net/smc: bpf: register smc_ops info struct_ops libbpf: fix error when st-prefix_ops and ops from differ btf bpf/selftests: add selftest for bpf_smc_ops include/net/netns/smc.h | 3 + include/net/smc.h | 51 ++ kernel/bpf/bpf_struct_ops.c | 2 + kernel/bpf/syscall.c | 1 + net/ipv4/tcp_output.c | 15 +- net/smc/Kconfig | 12 + net/smc/Makefile | 1 + net/smc/af_smc.c | 10 + net/smc/smc_ops.c | 150 +++++ net/smc/smc_ops.h | 31 + net/smc/smc_sysctl.c | 95 ++++ tools/lib/bpf/libbpf.c | 25 +- tools/testing/selftests/bpf/config | 4 + .../selftests/bpf/prog_tests/test_bpf_smc.c | 535 ++++++++++++++++++ tools/testing/selftests/bpf/progs/bpf_smc.c | 109 ++++ 15 files changed, 1032 insertions(+), 12 deletions(-) create mode 100644 net/smc/smc_ops.c create mode 100644 net/smc/smc_ops.h create mode 100644 tools/testing/selftests/bpf/prog_tests/test_bpf_smc.c create mode 100644 tools/testing/selftests/bpf/progs/bpf_smc.c