From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v1 0/5] BPF path manager, part 5
Date: Fri, 7 Feb 2025 18:49:23 +0800 [thread overview]
Message-ID: <cover.1738924875.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
Depends on:
- BPF path manager, part 4, v4
Based-on: <cover.1738919954.git.tanggeliang@kylinos.cn>
- add mptcp_address bpf_iter, v5
Based-on: <cover.1738924354.git.tanggeliang@kylinos.cn>
Geliang Tang (5):
bpf: Add mptcp path manager struct_ops
bpf: Register mptcp struct_ops kfunc set
selftests/bpf: Add mptcp userspace pm subtest
selftests/bpf: Implement mptcp pm helpers in BPF
selftests/bpf: Add mptcp bpf path manager subtest
net/mptcp/bpf.c | 372 +++++++++++++++++-
.../testing/selftests/bpf/prog_tests/mptcp.c | 211 ++++++++++
tools/testing/selftests/bpf/progs/mptcp_bpf.h | 185 +++++++++
.../bpf/progs/mptcp_bpf_userspace_pm.c | 275 +++++++++++++
4 files changed, 1042 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_userspace_pm.c
--
2.43.0
next reply other threads:[~2025-02-07 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 10:49 Geliang Tang [this message]
2025-02-07 10:49 ` [PATCH mptcp-next v1 1/5] bpf: Add mptcp path manager struct_ops Geliang Tang
2025-02-07 10:49 ` [PATCH mptcp-next v1 2/5] bpf: Register mptcp struct_ops kfunc set Geliang Tang
2025-02-07 10:49 ` [PATCH mptcp-next v1 3/5] selftests/bpf: Add mptcp userspace pm subtest Geliang Tang
2025-02-07 10:49 ` [PATCH mptcp-next v1 4/5] selftests/bpf: Implement mptcp pm helpers in BPF Geliang Tang
2025-02-07 10:49 ` [PATCH mptcp-next v1 5/5] selftests/bpf: Add mptcp bpf path manager subtest Geliang Tang
2025-02-07 10:57 ` [PATCH mptcp-next v1 0/5] BPF path manager, part 5 MPTCP CI
2025-02-07 11:15 ` MPTCP CI
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=cover.1738924875.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.