public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Wenjia Zhang <wenjia@linux.ibm.com>,
	kgraul@linux.ibm.com, jaka@linux.ibm.com, wintera@linux.ibm.com,
	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,
	tonylu@linux.alibaba.com, pabeni@redhat.com, edumazet@google.com
Subject: Re: [PATCH net-next v5 0/3] Introduce IPPROTO_SMC
Date: Mon, 3 Jun 2024 11:01:03 +0800	[thread overview]
Message-ID: <ee95457f-94d9-474c-9929-eda061cbf854@linux.alibaba.com> (raw)
In-Reply-To: <882713c2-02bd-4396-83be-c527b9d24eef@linux.ibm.com>



On 5/31/24 4:06 PM, Wenjia Zhang wrote:
>
>
> On 30.05.24 12:14, D. Wythe wrote:
>>
>>
>> On 5/30/24 5:30 PM, D. Wythe wrote:
>>> From: "D. Wythe" <alibuda@linux.alibaba.com>
>>>
>>> This patch allows to create smc socket via AF_INET,
>>> similar to the following code,
>>>
>>> /* create v4 smc sock */
>>> v4 = socket(AF_INET, SOCK_STREAM, IPPROTO_SMC);
>>>
>>> /* create v6 smc sock */
>>> v6 = socket(AF_INET6, SOCK_STREAM, IPPROTO_SMC);
>>
>> Welcome everyone to try out the eBPF based version of smc_run during 
>> testing, I have added a separate command called smc_run.bpf,
>> it was equivalent to normal smc_run but with IPPROTO_SMC via eBPF.
>>
>> You can obtain the code and more info from: 
>> https://github.com/D-Wythe/smc-tools
>>
>> Usage:
>>
>> smc_run.bpf
>> An eBPF implemented smc_run based on IPPROTO_SMC:
>>
>> 1. Support to transparent replacement based on command (Just like 
>> smc_run).
>> 2. Supprot to transparent replacement based on pid configuration. And 
>> supports the inheritance of this capability between parent and child 
>> processes.
>> 3. Support to transparent replacement based on per netns configuration.
>>
>> smc_run.bpf COMMAND
>>
>> 1. Equivalent to smc_run but with IPPROTO_SMC via eBPF
>>
>> smc_run.bpf -p pid
>>
>>   1. Add the process with target pid to the map. Afterward, all 
>> socket() calls of the process and its descendant processes will be 
>> replaced from IPPROTO_TCP to IPPROTO_SMC.
>>   2. Mapping will be automatically deleted when process exits.
>>   3. Specifically, COMMAND mode is actually works like following:
>>
>>      smc_run.bpf -p $$
>>      COMMAND
>>      exit
>>
>> smc_run.bpf -n 1
>>
>>   1. Make all socket() calls of the current netns to be replaced from 
>> IPPROTO_TCP to IPPROTO_SMC.
>>   2. Turn off it by smc_run.bpf -n 0
>>
>>
> Hi D. Wythe,
>
> Thank you for the info and description! The code generally looks good 
> to me, just still some details I need to check again. And I'd like to 
> give smc_run.bpf a try, and maybe let you know if it works for me next 
> week.
>
> Thanks,
> Wenjia

Hi Wenjia,

That's okay to us. And if there are any issues regarding the use of 
smc_run.bpf, please let me know.

Best wishes,
D. Wythe






  reply	other threads:[~2024-06-03  3:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30  9:30 [PATCH net-next v5 0/3] Introduce IPPROTO_SMC D. Wythe
2024-05-30  9:30 ` [PATCH net-next v5 1/3] net/smc: refactoring initialization of smc sock D. Wythe
2024-05-30  9:30 ` [PATCH net-next v5 2/3] net/smc: expose smc proto operations D. Wythe
2024-05-30  9:30 ` [PATCH net-next v5 3/3] net/smc: Introduce IPPROTO_SMC D. Wythe
2024-06-03  3:49   ` Ratheesh Kannoth
2024-06-03 14:43     ` D. Wythe
2024-05-30 10:14 ` [PATCH net-next v5 0/3] " D. Wythe
2024-05-31  8:06   ` Wenjia Zhang
2024-06-03  3:01     ` D. Wythe [this message]
2024-06-03  7:48   ` Niklas Schnelle
2024-06-03 15:07     ` D. Wythe
2024-06-04 11:32       ` Niklas Schnelle

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=ee95457f-94d9-474c-9929-eda061cbf854@linux.alibaba.com \
    --to=alibuda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --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=pabeni@redhat.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.com \
    --cc=wintera@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