From: "D. Wythe" <alibuda@linux.alibaba.com >
To: "D. Wythe" <alibuda@linux.alibaba.com>,
wenjia@linux.ibm.com, jaka@linux.ibm.com
Cc: 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 v7 0/6] net/smc: Introduce smc_ops
Date: Fri, 14 Feb 2025 17:22:09 +0800 [thread overview]
Message-ID: <20250214092209.GA88970@j66a10360.sqa.eu95> (raw)
In-Reply-To: <20250123015942.94810-1-alibuda@linux.alibaba.com>
On Thu, Jan 23, 2025 at 09:59:36AM +0800, D. Wythe wrote:
> This patch aims to introduce BPF injection capabilities for SMC and
> includes a self-test to ensure code stability.
>
> Since the SMC protocol isn't ideal for every situation, especially
> short-lived ones, most applications can't guarantee the absence of
> such scenarios. Consequently, applications may need specific strategies
> to decide whether to use SMC. For example, an application might limit SMC
> usage to certain IP addresses or ports.
>
> To maintain the principle of transparent replacement, we want applications
> to remain unaffected even if they need specific SMC strategies. In other
> words, they should not require recompilation of their code.
>
> Additionally, we need to ensure the scalability of strategy implementation.
> While using socket options or sysctl might be straightforward, it could
> complicate future expansions.
>
> Fortunately, BPF addresses these concerns effectively. Users can write
> their own strategies in eBPF to determine whether to use SMC, and they can
> easily modify those strategies in the future.
Hi smc folks, @Wenjia @Ian
Is there any feedback regarding this patches ? This series of code has
gone through multiple rounds of community reviews. However, the parts
related to SMC, including the new sysctl and ops name, really needs
your input and acknowledgment.
Additionally, this series includes a bug fix for SMC, which is easily
reproducible in the BPF CI tests.
Thanks,
D. Wythe
next prev parent reply other threads:[~2025-02-14 9:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 1:59 [PATCH bpf-next v7 0/6] net/smc: Introduce smc_ops D. Wythe
2025-01-23 1:59 ` [PATCH bpf-next v7 1/6] bpf: export necessary sympols for modules with struct_ops D. Wythe
2025-01-23 1:59 ` [PATCH bpf-next v7 2/6] net/smc: fix UAF on smcsk after smc_listen_out() D. Wythe
2025-01-23 2:21 ` Guangguan Wang
2025-01-23 1:59 ` [PATCH bpf-next v7 3/6] net/smc: Introduce generic hook smc_ops D. Wythe
2025-01-23 7:30 ` Dust Li
2025-01-23 10:15 ` Gerd Bayer
2025-02-05 8:02 ` D. Wythe
2025-01-23 1:59 ` [PATCH bpf-next v7 4/6] net/smc: bpf: register smc_ops info struct_ops D. Wythe
2025-01-23 1:59 ` [PATCH bpf-next v7 5/6] libbpf: fix error when st-prefix_ops and ops from differ btf D. Wythe
2025-01-23 1:59 ` [PATCH bpf-next v7 6/6] bpf/selftests: add selftest for bpf_smc_ops D. Wythe
2025-01-26 9:48 ` Zhu Yanjun
2025-01-23 7:33 ` [PATCH bpf-next v7 0/6] net/smc: Introduce smc_ops Dust Li
2025-02-14 9:22 ` D. Wythe [this message]
2025-02-14 11:37 ` Wenjia Zhang
2025-02-17 5:44 ` 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=20250214092209.GA88970@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