public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Wythe" <alibuda@linux.alibaba.com    >
To: Dust Li <dust.li@linux.alibaba.com>
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,
	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,
	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 v5 2/5] net/smc: Introduce generic hook smc_ops
Date: Tue, 14 Jan 2025 17:42:36 +0800	[thread overview]
Message-ID: <20250114094236.GA16797@j66a10360.sqa.eu95> (raw)
In-Reply-To: <20250113114012.GA89233@linux.alibaba.com>

On Mon, Jan 13, 2025 at 07:40:12PM +0800, Dust Li wrote:
> On 2025-01-07 12:17:12, D. Wythe wrote:
> >The introduction of IPPROTO_SMC enables eBPF programs to determine
> >whether to use SMC based on the context of socket creation, such as
> >network namespaces, PID and comm name, etc.
> >
> >As a subsequent enhancement, to introduce a new generic hook that
> >allows decisions on whether to use SMC or not at runtime, including
> >but not limited to local/remote IP address or ports.
> >
> >Moreover, in the future, we can achieve more complex extensions to the
> >protocol stack by extending this ops.
> >
> >Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
> >---
> > include/net/netns/smc.h |  3 ++
> > include/net/smc.h       | 51 ++++++++++++++++++++++
> > net/ipv4/tcp_output.c   | 15 +++++--
> > net/smc/Kconfig         | 12 ++++++
> > net/smc/Makefile        |  1 +
> > net/smc/smc_ops.c       | 51 ++++++++++++++++++++++
> > net/smc/smc_ops.h       | 25 +++++++++++
> > net/smc/smc_sysctl.c    | 95 +++++++++++++++++++++++++++++++++++++++++
> > 8 files changed, 249 insertions(+), 4 deletions(-)
> > create mode 100644 net/smc/smc_ops.c
> > create mode 100644 net/smc/smc_ops.h
> >
> >diff --git a/include/net/netns/smc.h b/include/net/netns/smc.h
> >index fc752a50f91b..59d069f56b2d 100644
> >--- a/include/net/netns/smc.h
> >+++ b/include/net/netns/smc.h
> >@@ -17,6 +17,9 @@ struct netns_smc {
> > #ifdef CONFIG_SYSCTL
> > 	struct ctl_table_header		*smc_hdr;
> > #endif
> >+#if IS_ENABLED(CONFIG_SMC_OPS)
> >+	struct smc_ops __rcu *ops;
>                               ^^^
> Align with other fields
> 
Oops, nice catch.
> >+#endif /* CONFIG_SMC_OPS */
> > 	unsigned int			sysctl_autocorking_size;
> > 	unsigned int			sysctl_smcr_buf_type;
> > 	int				sysctl_smcr_testlink_time;
> >diff --git a/include/net/smc.h b/include/net/smc.h
> >index db84e4e35080..326a217001d4 100644
> >--- a/include/net/smc.h
> >+++ b/include/net/smc.h
> >+#include <net/smc.h>
> 
> Put this include right after #include <net/proto_memory.h> ?
> I notice all the includes here are well classified.
> 
> 
Done, I didn't notice this detail before.
> > 
> > /* Refresh clocks of a TCP socket,
> >  * ensuring monotically increasing values.
> >@@ -759,14 +760,17 @@ static void tcp_options_write(struct tcphdr *th, struct tcp_sock *tp,
> > 	mptcp_options_write(th, ptr, tp, opts);
> > }
> > 
> >-static void smc_set_option(const struct tcp_sock *tp,
> >+static void smc_set_option(struct tcp_sock *tp,
> > 			   struct tcp_out_options *opts,
> > 			   unsigned int *remaining)
> > {
> >+	  SMC_OPS enables support to register genericfor hook via eBPF programs
> 
> genericfor ?
> 
generic.. I will fix it in next version. 
> >+	  for SMC subsystem. eBPF programs offer much greater flexibility
> >+	  in modifying the behavior of the SMC protocol stack compared
> >+	  to a complete kernel-based approach.
> >+
> >+	  if unsure, say N.
> >diff --git a/net/smc/Makefile b/net/smc/Makefile
> >index 60f1c87d5212..5dd706b2927a 100644
> >--- a/net/smc/Makefile
> >+++ b/net/smc/Makefile
> >+	struct net *net = container_of(ctl->data, struct net,
> >+				       smc.ops);
> 
> This line won't exceed 80 characters, no need to split into 2 lines.
> 
Take it. Thanks for all the advices.

Best wishes,
D. Wythe

> 
> Best regards,
> Dust

  reply	other threads:[~2025-01-14  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07  4:17 [PATCH bpf-next v5 0/5] net/smc: Introduce smc_ops D. Wythe
2025-01-07  4:17 ` [PATCH bpf-next v5 1/5] bpf: export necessary sympols for modules with struct_ops D. Wythe
2025-01-07  4:17 ` [PATCH bpf-next v5 2/5] net/smc: Introduce generic hook smc_ops D. Wythe
2025-01-13 11:40   ` Dust Li
2025-01-14  9:42     ` D. Wythe [this message]
2025-01-13 11:49   ` Dust Li
2025-01-14  9:51     ` D. Wythe
2025-01-07  4:17 ` [PATCH bpf-next v5 3/5] net/smc: bpf: register smc_ops info struct_ops D. Wythe
2025-01-07  4:17 ` [PATCH bpf-next v5 4/5] libbpf: fix error when st-prefix_ops and ops from differ btf D. Wythe
2025-01-07  4:17 ` [PATCH bpf-next v5 5/5] bpf/selftests: add selftest for bpf_smc_ops D. Wythe
2025-01-08  0:48   ` Martin KaFai Lau
2025-01-08 13:56     ` D. Wythe
2025-01-07  5:19 ` [PATCH bpf-next v5 0/5] net/smc: Introduce smc_ops 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=20250114094236.GA16797@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=dust.li@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