From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v3 0/5] BPF 'force to MPTCP'
Date: Mon, 3 Jul 2023 14:39:55 +0800 [thread overview]
Message-ID: <cover.1688366249.git.geliang.tang@suse.com> (raw)
v3:
- add a wrapper socket_create(), the bpf hooks will added in this
wrapper.
v2:
- Address issue #79 "allow 'force to MPTCP' mode: BPF".
- Define the prog in patch 3 in SEC "cgroup/sock_create" instead of
"sockops".
- Update other patches correspondingly.
v1:
This series depends on the two netns patches, should be inserted before
the BPF scheduler series:
selftests/bpf: use random netns name for mptcp
selftests/bpf: add two mptcp netns helpers
bpf: Add bpf_mptcpify helper
selftests/bpf: Test bpf_mptcpify helper
selftests/bpf: Add mptcpify selftest
mptcp: refactor push_pending logic
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/79
Geliang Tang (5):
Squash to "selftests/bpf: add two mptcp netns helpers"
net: socket: add socket_create wrapper
bpf: Add bpf_mptcpify helper
selftests/bpf: Test bpf_mptcpify helper
selftests/bpf: Add mptcpify selftest
include/linux/net.h | 6 +
include/uapi/linux/bpf.h | 7 +
kernel/trace/bpf_trace.c | 23 ++++
net/socket.c | 12 +-
tools/include/uapi/linux/bpf.h | 7 +
.../testing/selftests/bpf/prog_tests/mptcp.c | 127 +++++++++++++++---
tools/testing/selftests/bpf/progs/mptcpify.c | 16 +++
7 files changed, 177 insertions(+), 21 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/mptcpify.c
--
2.35.3
next reply other threads:[~2023-07-03 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 6:39 Geliang Tang [this message]
2023-07-03 6:39 ` [PATCH mptcp-next v3 1/5] Squash to "selftests/bpf: add two mptcp netns helpers" Geliang Tang
2023-07-03 6:39 ` [PATCH mptcp-next v3 2/5] net: socket: add socket_create wrapper Geliang Tang
2023-07-03 10:07 ` kernel test robot
2023-07-03 10:48 ` kernel test robot
2023-07-03 6:39 ` [PATCH mptcp-next v3 3/5] bpf: Add bpf_mptcpify helper Geliang Tang
2023-07-21 1:20 ` kernel test robot
2023-07-03 6:39 ` [PATCH mptcp-next v3 4/5] selftests/bpf: Test " Geliang Tang
2023-07-03 6:40 ` [PATCH mptcp-next v3 5/5] selftests/bpf: Add mptcpify selftest Geliang Tang
2023-07-03 7:52 ` selftests/bpf: Add mptcpify selftest: Tests Results 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.1688366249.git.geliang.tang@suse.com \
--to=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/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