From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v9 0/4] setsockopt per subflow: BPF
Date: Wed, 24 Apr 2024 09:13:50 +0800 [thread overview]
Message-ID: <cover.1713920939.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v9:
- validate the return value of snprintf in patch 2 as Mat suggested.
- patch 2 depends on "selftests/bpf: Add RUN_MPTCP_TEST macro", so this
series could be merged in this order:
1 selftests/bpf: Add mptcp subflow example
2 selftests/bpf: Add RUN_MPTCP_TEST macro
3 selftests/bpf: Add mptcp subflow subtest
4 selftests/bpf: Handle SIGINT when creating netns
v8:
- update the git metadata to add Nicolas as the git "Author" and add a
"Co-authored-by" tag with my name in patch 1 as Mat suggested in v7.
- use send_byte in patch 2 instead of send_recv_data, to make this
series independent of the commit "selftests/bpf: Export send_recv_data
helper", which is in bpf-next, but not in mptcp_net-next at this moment.
v7:
- address Mat's comments in v6 (thanks): drop MPTCP_BASE_TEST and rebased.
- depends on:
"refactor mptcp bpf tests" v7
"export send_byte and send_recv_data" v2
v6:
- Deponds on "[bpf-next] export send_byte and send_recv_data" series.
v5:
- #1-#7 Address #76: add new macros MPTCP_BASE_TEST and RUN_MPTCP_TEST.
- #8-#14 add MPTCP_SCHED_TEST macro.
v4:
- #1-#5 Address #76: add a new macro RUN_MPTCP_TEST.
- #6-#11 Cleanups: add send_data_and_verify and SCHED_TEST.
v3:
- deal with EAGAIN.
- add _ss_search helper.
v2:
- fix checkpatch warnings.
- cleanups.
Geliang Tang (3):
selftests/bpf: Add mptcp subflow subtest
selftests/bpf: Handle SIGINT when creating netns
Squash to "selftests/bpf: Add bpf scheduler test"
Nicolas Rybowski (1):
selftests/bpf: Add mptcp subflow example
.../testing/selftests/bpf/prog_tests/mptcp.c | 143 +++++++++++++++---
.../selftests/bpf/progs/mptcp_subflow.c | 70 +++++++++
2 files changed, 195 insertions(+), 18 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_subflow.c
--
2.40.1
next reply other threads:[~2024-04-24 1:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 1:13 Geliang Tang [this message]
2024-04-24 1:13 ` [PATCH mptcp-next v9 1/4] selftests/bpf: Add mptcp subflow example Geliang Tang
2024-04-24 1:13 ` [PATCH mptcp-next v9 2/4] selftests/bpf: Add mptcp subflow subtest Geliang Tang
2024-04-24 1:13 ` [PATCH mptcp-next v9 3/4] selftests/bpf: Handle SIGINT when creating netns Geliang Tang
2024-04-24 1:13 ` [PATCH mptcp-next v9 4/4] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-04-24 2:33 ` [PATCH mptcp-next v9 0/4] setsockopt per subflow: BPF MPTCP CI
2024-04-24 15:37 ` Mat Martineau
2024-04-29 18:38 ` Matthieu Baerts
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.1713920939.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 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).