From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v2 00/15] refactor mptcp bpf tests
Date: Fri, 29 Mar 2024 12:55:56 +0800 [thread overview]
Message-ID: <cover.1711688054.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
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 (15):
Squash to "selftests/bpf: Add bpf scheduler test" - fix
selftests/bpf: Handle EAGAIN in bpf_tcp_ca
selftests/bpf: Export send_single_byte helper
selftests/bpf: Export send_recv_data helper
selftests/bpf: Refactor mptcp_sock test
selftests/bpf: Refactor mptcpify test
selftests/bpf: Add MPTCP_BASE_TEST macro
selftests/bpf: Add RUN_MPTCP_TEST macro
Squash to "selftests/bpf: Add bpf scheduler test"
Squash to "selftests/bpf: Add bpf_first test"
Squash to "selftests/bpf: Add bpf_bkup test"
Squash to "selftests/bpf: Add bpf_rr test"
Squash to "selftests/bpf: Add bpf_red test"
Squash to "selftests/bpf: Add bpf_burst test"
Squash to "selftests/bpf: Add bpf scheduler test" 2
tools/testing/selftests/bpf/network_helpers.c | 85 ++++
tools/testing/selftests/bpf/network_helpers.h | 2 +
.../selftests/bpf/prog_tests/bpf_tcp_ca.c | 72 +--
.../testing/selftests/bpf/prog_tests/mptcp.c | 468 +++++-------------
.../selftests/bpf/prog_tests/tcp_rtt.c | 9 +-
5 files changed, 208 insertions(+), 428 deletions(-)
--
2.40.1
next reply other threads:[~2024-03-29 4:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 4:55 Geliang Tang [this message]
2024-03-29 4:55 ` [PATCH mptcp-next v2 01/15] Squash to "selftests/bpf: Add bpf scheduler test" - fix Geliang Tang
2024-03-29 4:55 ` [PATCH mptcp-next v2 02/15] selftests/bpf: Handle EAGAIN in bpf_tcp_ca Geliang Tang
2024-03-29 4:55 ` [PATCH mptcp-next v2 03/15] selftests/bpf: Export send_single_byte helper Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 04/15] selftests/bpf: Export send_recv_data helper Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 05/15] selftests/bpf: Refactor mptcp_sock test Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 06/15] selftests/bpf: Refactor mptcpify test Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 07/15] selftests/bpf: Add MPTCP_BASE_TEST macro Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 08/15] selftests/bpf: Add RUN_MPTCP_TEST macro Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 09/15] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 10/15] Squash to "selftests/bpf: Add bpf_first test" Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 11/15] Squash to "selftests/bpf: Add bpf_bkup test" Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 12/15] Squash to "selftests/bpf: Add bpf_rr test" Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 13/15] Squash to "selftests/bpf: Add bpf_red test" Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 14/15] Squash to "selftests/bpf: Add bpf_burst test" Geliang Tang
2024-03-29 4:56 ` [PATCH mptcp-next v2 15/15] Squash to "selftests/bpf: Add bpf scheduler test" 2 Geliang Tang
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.1711688054.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).