From: Jakub Kicinski <kuba@kernel.org>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
ast@kernel.org, daniel@iogearbox.net, andrii@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, 28 Feb 2023 15:02:59 -0800 [thread overview]
Message-ID: <20230228150259.6b526bef@kernel.org> (raw)
In-Reply-To: <1677602291-1666-1-git-send-email-alibuda@linux.alibaba.com>
On Wed, 1 Mar 2023 00:38:07 +0800 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.
If you cross-posting to net please make sure you follow netdev rules.
Don't repost too often.
next prev parent reply other threads:[~2023-02-28 23:03 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 ` Jakub Kicinski [this message]
2023-03-01 2:36 ` [PATCH bpf-next v4 0/4] net/smc: Introduce BPF injection capability D. Wythe
2023-03-07 3:05 ` D. Wythe
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=20230228150259.6b526bef@kernel.org \
--to=kuba@kernel.org \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).