From: "D. Wythe" <alibuda@linux.alibaba.com>
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
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: Re: [RFC PATCH bpf-next 0/5] net/smc: Introduce BPF injection capability
Date: Wed, 12 Apr 2023 16:33:21 +0800 [thread overview]
Message-ID: <acb77026-c8eb-39e8-b3a8-23c348cbd60c@linux.alibaba.com> (raw)
In-Reply-To: <1680795034-86384-1-git-send-email-alibuda@linux.alibaba.com>
Hi everyone,
It's seems the RFC patch been hanging for some time. I would like to
politely inquire if there are any suggestions or criticisms.
Compared to previous patches, this patch has several main features:
1. Allow registration of multiple negotiators, each SMC negotiator has a
name and can be indexed that name
2. no read/write lock anymore
3. support bpf update
If you have any suggestions or criticisms, please let me know.
Thanks
D. Wythe
On 4/6/23 11:30 PM, D. Wythe wrote:
> From: "D. Wythe" <alibuda@linux.alibaba.com>
>
> This patches attempt to introduce BPF injection capability for SMC,
> and add selftest to ensure code stability.
>
> As we all know that the SMC protocol is not suitable for all scenarios,
> especially for short-lived. However, 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.
>
> This patches implement injection capability for SMC via struct_ops.
> In that way, we can add new injection scenarios in the future.
>
> D. Wythe (5):
> net/smc: move smc_sock related structure definition
> net/smc: net/smc: allow smc to negotiate protocols on policies
> net/smc: allow set or get smc negotiator by sockopt
> bpf: add smc negotiator support in BPF struct_ops
> bpf/selftests: add selftest for SMC bpf capability
>
> include/net/smc.h | 268 +++++++++++++++++
> include/uapi/linux/smc.h | 1 +
> kernel/bpf/bpf_struct_ops_types.h | 4 +
> net/Makefile | 1 +
> net/smc/Kconfig | 13 +
> net/smc/af_smc.c | 203 ++++++++++---
> net/smc/bpf_smc.c | 359 +++++++++++++++++++++++
> net/smc/smc.h | 224 --------------
> tools/testing/selftests/bpf/prog_tests/bpf_smc.c | 107 +++++++
> tools/testing/selftests/bpf/progs/bpf_smc.c | 265 +++++++++++++++++
> 10 files changed, 1186 insertions(+), 259 deletions(-)
> create mode 100644 net/smc/bpf_smc.c
> create mode 100644 tools/testing/selftests/bpf/prog_tests/bpf_smc.c
> create mode 100644 tools/testing/selftests/bpf/progs/bpf_smc.c
>
prev parent reply other threads:[~2023-04-12 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 15:30 [RFC PATCH bpf-next 0/5] net/smc: Introduce BPF injection capability D. Wythe
2023-04-06 15:30 ` [RFC PATCH bpf-next 1/5] net/smc: move smc_sock related structure definition D. Wythe
2023-04-06 15:30 ` [RFC PATCH bpf-next 2/5] net/smc: net/smc: allow smc to negotiate protocols on policies D. Wythe
2023-04-06 15:30 ` [RFC PATCH bpf-next 3/5] net/smc: allow set or get smc negotiator by sockopt D. Wythe
2023-04-06 15:30 ` [RFC PATCH bpf-next 4/5] bpf: add smc negotiator support in BPF struct_ops D. Wythe
2023-04-06 15:30 ` [RFC PATCH bpf-next 5/5] bpf/selftests: add selftest for SMC bpf capability D. Wythe
2023-04-12 8:33 ` D. Wythe [this message]
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=acb77026-c8eb-39e8-b3a8-23c348cbd60c@linux.alibaba.com \
--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=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--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=wenjia@linux.ibm.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