From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v6 00/11] BPF packet scheduler
Date: Wed, 1 Jun 2022 22:08:13 +0800 [thread overview]
Message-ID: <cover.1654092153.git.geliang.tang@suse.com> (raw)
v6:
- fix the warning reported by kernel test robot:
>> net/mptcp/bpf.c:165:6: warning: no previous prototype for 'bpf_mptcp_subflow_set_scheduled' [-Wmissing-prototypes]
165 | void bpf_mptcp_subflow_set_scheduled(struct mptcp_subflow_context *subflow)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- rename bpf_mptcp_subflow_set_scheduled to mptcp_subflow_set_scheduled
v5:
- add bpf_mptcp_subflow_set_scheduled helper.
- drop padding bits before backup, use BPF_CORE_READ_BITFIELD_PROBED()
instead.
- The new patch "mptcp: add bpf set scheduled helper" should be inserted
between the commits "mptcp: add bpf_mptcp_sched_ops" and
"selftests/bpf: add bpf_first scheduler"
v4:
- merge "mptcp: move is_scheduled into mptcp_subflow_context"
- rename bpf_backup tp bpf_bkup
- full patches of this series: https://github.com/geliangtang/mptcp_net-next
v3:
- use new BPF scheduler API:
- add backup scheduler
- add round-robin scheduler
- check bytes_sent of 'ss' output.
v2:
- Use new BPF scheduler API:
unsigned long (*get_subflow)(const struct mptcp_sock *msk, bool reinject,
struct mptcp_sched_data *data);
Geliang Tang (11):
Squash to "mptcp: add struct mptcp_sched_ops"
Squash to "mptcp: add sched in mptcp_sock"
Squash to "mptcp: add get_subflow wrappers"
Squash to "mptcp: add bpf_mptcp_sched_ops"
mptcp: add subflow_set_scheduled helper
Squash to "selftests/bpf: add bpf_first scheduler"
Squash to "selftests/bpf: add bpf_first test"
selftests/bpf: add bpf_bkup scheduler
selftests/bpf: add bpf_bkup test
selftests/bpf: add bpf_rr scheduler
selftests/bpf: add bpf_rr test
include/net/mptcp.h | 7 +-
net/mptcp/bpf.c | 34 ++++---
net/mptcp/protocol.h | 3 +
net/mptcp/sched.c | 60 ++++++++++---
tools/testing/selftests/bpf/bpf_tcp_helpers.h | 17 +++-
.../testing/selftests/bpf/prog_tests/mptcp.c | 89 ++++++++++++++++++-
.../selftests/bpf/progs/mptcp_bpf_bkup.c | 43 +++++++++
.../selftests/bpf/progs/mptcp_bpf_first.c | 5 +-
.../selftests/bpf/progs/mptcp_bpf_rr.c | 46 ++++++++++
9 files changed, 272 insertions(+), 32 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_bkup.c
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_rr.c
--
2.34.1
next reply other threads:[~2022-06-01 14:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 14:08 Geliang Tang [this message]
2022-06-01 14:08 ` [PATCH mptcp-next v6 01/11] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 02/11] Squash to "mptcp: add sched in mptcp_sock" Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 03/11] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 04/11] Squash to "mptcp: add bpf_mptcp_sched_ops" Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 05/11] mptcp: add subflow_set_scheduled helper Geliang Tang
2022-06-02 0:23 ` Mat Martineau
2022-06-01 14:08 ` [PATCH mptcp-next v6 06/11] Squash to "selftests/bpf: add bpf_first scheduler" Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 07/11] Squash to "selftests/bpf: add bpf_first test" Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 08/11] selftests/bpf: add bpf_bkup scheduler Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 09/11] selftests/bpf: add bpf_bkup test Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 10/11] selftests/bpf: add bpf_rr scheduler Geliang Tang
2022-06-01 14:08 ` [PATCH mptcp-next v6 11/11] selftests/bpf: add bpf_rr test Geliang Tang
2022-06-01 14:21 ` selftests/bpf: add bpf_rr test: Build Failure MPTCP CI
2022-06-01 15:04 ` Matthieu Baerts
2022-06-01 22:25 ` Geliang Tang
2022-06-01 16:02 ` selftests/bpf: add bpf_rr test: Tests Results MPTCP CI
2022-06-02 0:02 ` [PATCH mptcp-next v6 00/11] BPF packet scheduler Mat Martineau
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.1654092153.git.geliang.tang@suse.com \
--to=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/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