From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v8 0/9] refactor mptcp bpf tests
Date: Wed, 10 Apr 2024 10:05:15 +0800 [thread overview]
Message-ID: <cover.1712714407.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v8:
- change argument types of send_data_and_verify from strings to
booleans as Matt suggested.
v7:
- address Matt's comments in v6 (thanks)
- add more commit logs.
- use WITH_DATA/WITHOUT_DATA instead of 1/0.
- make patch 3 as a squash-to patch.
v6:
- drop patch 1 in v5 and rebased.
v5:
- drop patch 5 in v4:
Squash to "selftests/bpf: Add bpf scheduler test" 4 cleanup
v4:
- add set_nonblock to make BPF tests stable.
- split 'Squash to "selftests/bpf: Add bpf scheduler test"' into 4 patches.
v3:
- part 1, bpf schedulers.
v2:
- add two more helpers, send_single_byte and send_recv_data.
Refactor mptcp bpf tests using newly added macros MPTCP_BASE_TEST,
RUN_MPTCP_TEST and MPTCP_SCHED_TEST macro.
Geliang Tang (9):
selftests/bpf: Add RUN_MPTCP_TEST macro
Squash to "selftests/bpf: Add bpf scheduler test" 1 verify
Squash to "selftests/bpf: Add bpf scheduler test" 2 time
Squash to "selftests/bpf: Add bpf scheduler test" 3 MPTCP_SCHED_TEST
Squash to "selftests/bpf: Add bpf_first scheduler & test"
Squash to "selftests/bpf: Add bpf_bkup scheduler & test"
Squash to "selftests/bpf: Add bpf_rr scheduler & test"
Squash to "selftests/bpf: Add bpf_red scheduler & test"
Squash to "selftests/bpf: Add bpf_burst scheduler & test"
.../testing/selftests/bpf/prog_tests/mptcp.c | 267 +++++-------------
.../selftests/bpf/progs/mptcp_bpf_bkup.c | 1 +
.../selftests/bpf/progs/mptcp_bpf_burst.c | 1 +
.../selftests/bpf/progs/mptcp_bpf_first.c | 1 +
.../selftests/bpf/progs/mptcp_bpf_red.c | 1 +
.../selftests/bpf/progs/mptcp_bpf_rr.c | 1 +
6 files changed, 79 insertions(+), 193 deletions(-)
--
2.40.1
next reply other threads:[~2024-04-10 2:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 2:05 Geliang Tang [this message]
2024-04-10 2:05 ` [PATCH mptcp-next v8 1/9] selftests/bpf: Add RUN_MPTCP_TEST macro Geliang Tang
2024-04-10 2:05 ` [PATCH mptcp-next v8 2/9] Squash to "selftests/bpf: Add bpf scheduler test" 1 verify Geliang Tang
2024-04-10 2:05 ` [PATCH mptcp-next v8 3/9] Squash to "selftests/bpf: Add bpf scheduler test" 2 time Geliang Tang
2024-04-10 2:05 ` [PATCH mptcp-next v8 4/9] Squash to "selftests/bpf: Add bpf scheduler test" 3 MPTCP_SCHED_TEST Geliang Tang
2024-04-12 23:30 ` Mat Martineau
2024-04-10 2:05 ` [PATCH mptcp-next v8 5/9] Squash to "selftests/bpf: Add bpf_first scheduler & test" Geliang Tang
2024-04-12 23:32 ` Mat Martineau
2024-04-10 2:05 ` [PATCH mptcp-next v8 6/9] Squash to "selftests/bpf: Add bpf_bkup " Geliang Tang
2024-04-10 2:05 ` [PATCH mptcp-next v8 7/9] Squash to "selftests/bpf: Add bpf_rr " Geliang Tang
2024-04-10 2:05 ` [PATCH mptcp-next v8 8/9] Squash to "selftests/bpf: Add bpf_red " Geliang Tang
2024-04-10 2:05 ` [PATCH mptcp-next v8 9/9] Squash to "selftests/bpf: Add bpf_burst " Geliang Tang
2024-04-10 2:52 ` [PATCH mptcp-next v8 0/9] refactor mptcp bpf tests MPTCP CI
2024-04-10 16:50 ` 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.1712714407.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 read-only IMAP folder(s) and NNTP newsgroup(s).