From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next 00/10] BPF packet scheduler
Date: Fri, 20 May 2022 16:04:45 +0800 [thread overview]
Message-ID: <cover.1653033459.git.geliang.tang@suse.com> (raw)
- Use new BPF scheduler API
- merged "BPF round-robin scheduler" v14
- merged "BPF redundant scheduler" v2
- base-commit: export/20220519T160645
- This series will break two link failure tests:
Created /tmp/tmp.bTGaRxJupX (size 1 KB) containing data sent by client
Created /tmp/tmp.K2Llsy3W03 (size 1 KB) containing data sent by server
Created /tmp/tmp.4uLEQcKbee (size 23622 KB) containing data sent by client
001 multiple flows, signal, link failure syn[ ok ] - synack[ ok ] - ack[ ok ]
add[ ok ] - echo [ ok ]
stale [ ok ]
Created /tmp/tmp.hV4OKPkqoH (size 12288 KB) containing data sent by server
002 multi flows, signal, bidi, link fail syn[ ok ] - synack[ ok ] - ack[ ok ]
add[ ok ] - echo [ ok ]
stale [ ok ]
003 backup subflow unused, link failure syn[ ok ] - synack[ ok ] - ack[ ok ]
add[ ok ] - echo [ ok ]
link usage [ ok ]
004 backup flow used, multi links fail syn[ ok ] - synack[ ok ] - ack[ ok ]
add[ ok ] - echo [ ok ]
stale [ ok ]
link usage [fail] got 11% usage, expected 50%
005 backup flow used, bidi, link failure syn[ ok ] - synack[ ok ] - ack[ ok ]
add[ ok ] - echo [ ok ]
stale [ ok ]
link usage [fail] got 10% usage, expected 50%
2 failure(s) has(ve) been detected:
- 4: backup flow used, multi links fail
- 5: backup flow used, bidi, link failure
Geliang Tang (10):
Squash to "mptcp: add struct mptcp_sched_ops"
mptcp: reflect first flag in subflow_push_pending
Squash to "mptcp: add get_subflow wrappers"
Squash to "mptcp: add bpf_mptcp_sched_ops"
mptcp: add subflows array in sched data
Squash to "selftests/bpf: add bpf_first scheduler"
selftests/bpf: add bpf_rr scheduler
selftests/bpf: add bpf_rr test
selftests/bpf: add bpf_red scheduler
selftests/bpf: add bpf_red test
include/net/mptcp.h | 5 +-
net/mptcp/bpf.c | 7 +-
net/mptcp/protocol.c | 201 ++++++++++++------
net/mptcp/protocol.h | 5 +-
net/mptcp/sched.c | 107 ++++++++--
tools/testing/selftests/bpf/bpf_tcp_helpers.h | 22 +-
.../testing/selftests/bpf/prog_tests/mptcp.c | 76 +++++++
.../selftests/bpf/progs/mptcp_bpf_first.c | 6 +-
.../selftests/bpf/progs/mptcp_bpf_red.c | 39 ++++
.../selftests/bpf/progs/mptcp_bpf_rr.c | 48 +++++
10 files changed, 419 insertions(+), 97 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_red.c
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_rr.c
--
2.34.1
next reply other threads:[~2022-05-20 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 8:04 Geliang Tang [this message]
2022-05-20 8:04 ` [PATCH mptcp-next 01/10] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 02/10] mptcp: reflect first flag in subflow_push_pending Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 03/10] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 04/10] Squash to "mptcp: add bpf_mptcp_sched_ops" Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 05/10] mptcp: add subflows array in sched data Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 06/10] Squash to "selftests/bpf: add bpf_first scheduler" Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 07/10] selftests/bpf: add bpf_rr scheduler Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 08/10] selftests/bpf: add bpf_rr test Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 09/10] selftests/bpf: add bpf_red scheduler Geliang Tang
2022-05-20 8:04 ` [PATCH mptcp-next 10/10] selftests/bpf: add bpf_red test Geliang Tang
2022-05-20 8:17 ` selftests/bpf: add bpf_red test: Build Failure MPTCP CI
2022-05-20 9:52 ` selftests/bpf: add bpf_red test: Tests Results 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.1653033459.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;
as well as URLs for NNTP newsgroup(s).