From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v1 0/8] cleanups for bpf schedulers
Date: Thu, 6 Mar 2025 10:15:32 +0800 [thread overview]
Message-ID: <cover.1741226722.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
1. Add validate_scheduler.
2. Drop mptcp_sched_find in bpf_mptcp_sched_init_member.
3. Drop mptcp_sock_type and mptcp_subflow_type.
4. Move netns_new() out of sched_init().
5. Use .struct_ops.link instead of .struct_ops.
Geliang Tang (8):
mptcp: add mptcp_validate_scheduler helper
Squash to "bpf: Add bpf_mptcp_sched_ops"
Squash to "selftests/bpf: Add bpf scheduler 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"
net/mptcp/bpf.c | 32 +++++++------
net/mptcp/protocol.h | 1 +
net/mptcp/sched.c | 17 ++++++-
.../testing/selftests/bpf/prog_tests/mptcp.c | 45 ++++++++++---------
tools/testing/selftests/bpf/progs/mptcp_bpf.h | 3 --
.../selftests/bpf/progs/mptcp_bpf_bkup.c | 2 +-
.../selftests/bpf/progs/mptcp_bpf_burst.c | 10 ++---
.../selftests/bpf/progs/mptcp_bpf_first.c | 2 +-
.../selftests/bpf/progs/mptcp_bpf_red.c | 2 +-
.../selftests/bpf/progs/mptcp_bpf_rr.c | 2 +-
10 files changed, 63 insertions(+), 53 deletions(-)
--
2.43.0
next reply other threads:[~2025-03-06 2:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 2:15 Geliang Tang [this message]
2025-03-06 2:15 ` [PATCH mptcp-next v1 1/8] mptcp: add mptcp_validate_scheduler helper Geliang Tang
2025-03-18 1:09 ` Mat Martineau
2025-03-06 2:15 ` [PATCH mptcp-next v1 2/8] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2025-03-06 2:15 ` [PATCH mptcp-next v1 3/8] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2025-03-18 1:11 ` Mat Martineau
2025-03-20 19:38 ` Matthieu Baerts
2025-03-06 2:15 ` [PATCH mptcp-next v1 4/8] Squash to "selftests/bpf: Add bpf_first scheduler & test" Geliang Tang
2025-03-06 2:15 ` [PATCH mptcp-next v1 5/8] Squash to "selftests/bpf: Add bpf_bkup " Geliang Tang
2025-03-06 2:15 ` [PATCH mptcp-next v1 6/8] Squash to "selftests/bpf: Add bpf_rr " Geliang Tang
2025-03-06 2:15 ` [PATCH mptcp-next v1 7/8] Squash to "selftests/bpf: Add bpf_red " Geliang Tang
2025-03-06 2:15 ` [PATCH mptcp-next v1 8/8] Squash to "selftests/bpf: Add bpf_burst " Geliang Tang
2025-03-06 3:26 ` [PATCH mptcp-next v1 0/8] cleanups for bpf schedulers MPTCP CI
2025-03-20 17:31 ` 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.1741226722.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.