From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v7 0/4] fixes for "new MPTCP subflow subtest v4"
Date: Tue, 3 Sep 2024 16:04:56 +0800 [thread overview]
Message-ID: <cover.1725350462.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v7:
- drop helpers mptcp_for_each_subflow_safe and
list_for_each_entry_safe.
- update parameters of _check_getsockopt_subflow_mark/cc.
- print more messages in the logs as Matt suggested.
v6:
- address Matt's comments in v5.
- use mptcp_for_each_subflow in _check_getsockopt_subflow_mark.
- check msk->pm.subflows in _check_getsockopt_subflow_mark/cc.
- add wait_for_new_subflows helper.
v5:
- rename _check_getsockopt_subflows_mark in patch 1.
- address Matt's comments in v4.
v4:
- address Matt's comments in v3.
v3:
- drop "ss_search" from subflow subtest
- fix mptcp_for_each_subflow_safe
- add cond_break in list_for_each_entry/_safe
Two fixes address Martin's comments in "new MPTCP subflow subtest" v4.
Patch 2 will conflict with "selftests/bpf: Add bpf_first scheduler & test".
Geliang Tang (4):
Squash to "selftests/bpf: Add mptcp subflow example"
selftests/bpf: Add getsockopt to inspect mptcp subflow
Squash to "selftests/bpf: Add mptcp subflow subtest"
Squash to "selftests/bpf: Add bpf scheduler test"
.../testing/selftests/bpf/prog_tests/mptcp.c | 65 ++++++++-----
tools/testing/selftests/bpf/progs/mptcp_bpf.h | 27 ++++++
.../selftests/bpf/progs/mptcp_subflow.c | 92 ++++++++++++++++++-
3 files changed, 162 insertions(+), 22 deletions(-)
--
2.43.0
next reply other threads:[~2024-09-03 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 8:04 Geliang Tang [this message]
2024-09-03 8:04 ` [PATCH mptcp-next v7 1/4] Squash to "selftests/bpf: Add mptcp subflow example" Geliang Tang
2024-09-03 8:04 ` [PATCH mptcp-next v7 2/4] selftests/bpf: Add getsockopt to inspect mptcp subflow Geliang Tang
2024-09-03 9:11 ` Matthieu Baerts
2024-09-03 9:16 ` Matthieu Baerts
2024-09-04 9:55 ` Geliang Tang
2024-09-04 10:29 ` Matthieu Baerts
2024-09-04 10:09 ` Geliang Tang
2024-09-04 10:35 ` Matthieu Baerts
2024-09-03 8:04 ` [PATCH mptcp-next v7 3/4] Squash to "selftests/bpf: Add mptcp subflow subtest" Geliang Tang
2024-09-03 8:05 ` [PATCH mptcp-next v7 4/4] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-09-03 8:59 ` [PATCH mptcp-next v7 0/4] fixes for "new MPTCP subflow subtest v4" 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.1725350462.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