From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v2 0/5] BPF redundant scheduler
Date: Wed, 11 May 2022 20:17:40 +0800 [thread overview]
Message-ID: <cover.1652271034.git.geliang.tang@suse.com> (raw)
v2:
- add MPTCP_SUBFLOWS_MAX limit to avoid infinite loops when the
scheduler always sets call_again to true.
- track the largest copied amount.
- deal with __mptcp_subflow_push_pending() and the retransmit loop.
- depends on "BPF round-robin scheduler" v14.
v1:
Implements the redundant BPF MPTCP scheduler, which sends all packets
redundantly on all available subflows.
depends on:
- BPF round-robin scheduler, v13
Geliang Tang (5):
Squash to "mptcp: add get_subflow wrappers"
mptcp: add redundant subflows support
mptcp: add call_again flag in mptcp_sched_ops
selftests/bpf: add bpf_red scheduler
selftests/bpf: add bpf_red test
include/net/mptcp.h | 1 +
net/mptcp/protocol.c | 64 ++++++++++++++-----
net/mptcp/protocol.h | 4 +-
net/mptcp/sched.c | 11 +++-
.../testing/selftests/bpf/prog_tests/mptcp.c | 38 +++++++++++
.../selftests/bpf/progs/mptcp_bpf_red.c | 54 ++++++++++++++++
6 files changed, 151 insertions(+), 21 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_red.c
--
2.34.1
next reply other threads:[~2022-05-11 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 12:17 Geliang Tang [this message]
2022-05-11 12:17 ` [PATCH mptcp-next v2 1/5] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-05-11 12:17 ` [PATCH mptcp-next v2 2/5] mptcp: add redundant subflows support Geliang Tang
2022-05-11 12:17 ` [PATCH mptcp-next v2 3/5] mptcp: add call_again flag in mptcp_sched_ops Geliang Tang
2022-05-11 12:17 ` [PATCH mptcp-next v2 4/5] selftests/bpf: add bpf_red scheduler Geliang Tang
2022-05-11 12:17 ` [PATCH mptcp-next v2 5/5] selftests/bpf: add bpf_red test Geliang Tang
2022-05-13 1:15 ` [PATCH mptcp-next v2 0/5] BPF redundant 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.1652271034.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