public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
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
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: [PATCH bpf-next v4 0/4] net/smc: Introduce BPF injection capability
Date: Tue, 7 Mar 2023 11:05:46 +0800	[thread overview]
Message-ID: <25cee0eb-a1f9-9f0b-9987-ca6e79e6b752@linux.alibaba.com> (raw)
In-Reply-To: <1677602291-1666-1-git-send-email-alibuda@linux.alibaba.com>



On 3/1/23 12:38 AM, 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.
>
> v4 -> v3:
>      1. fix compile error and warning
>
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/oe-kbuild-all/202302282100.x7qq7PGX-lkp@intel.com/

Hi Wenjia and all,

I wondering if there are any more questions about this PATCH, This patch 
seems to have been hanging for some time.

If you have any questions, please let me know.


Thanks,

D. Wythe


Do you have any questions about this PATCH?  If you have any other 
questions, please let me know.


  parent reply	other threads:[~2023-03-07  3:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 16:38 [PATCH bpf-next v4 0/4] net/smc: Introduce BPF injection capability D. Wythe
2023-02-28 16:38 ` [PATCH bpf-next v4 1/4] net/smc: move smc_sock related structure definition D. Wythe
2023-03-08  9:48   ` Tony Lu
2023-02-28 16:38 ` [PATCH bpf-next v4 2/4] bpf: add SMC support in BPF struct_ops D. Wythe
2023-02-28 16:38 ` [PATCH bpf-next v4 3/4] net/smc: add BPF injection on smc negotiation D. Wythe
2023-02-28 16:38 ` [PATCH bpf-next v4 4/4] bpf/selftests: add selftest for SMC bpf capability D. Wythe
2023-02-28 23:02 ` [PATCH bpf-next v4 0/4] net/smc: Introduce BPF injection capability Jakub Kicinski
2023-03-01  2:36   ` D. Wythe
2023-03-07  3:05 ` D. Wythe [this message]
2023-03-07 16:44   ` Martin KaFai Lau
2023-03-08  5:58     ` 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=25cee0eb-a1f9-9f0b-9987-ca6e79e6b752@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=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