MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next 0/4] BPF redundant scheduler
Date: Mon,  9 May 2022 23:01:06 +0800	[thread overview]
Message-ID: <cover.1652108279.git.geliang.tang@suse.com> (raw)

Implements the redundant BPF MPTCP scheduler, which sends all packets
redundantly on all available subflows.

depends on:
 - BPF round-robin scheduler, v13

Geliang Tang (4):
  Squash to "mptcp: add get_subflow wrappers"
  mptcp: add redundant subflows support
  selftests/bpf: add bpf_red scheduler
  selftests/bpf: add bpf_red test

 include/net/mptcp.h                           |  1 +
 net/mptcp/protocol.c                          | 26 ++++++----
 net/mptcp/protocol.h                          |  4 +-
 net/mptcp/sched.c                             | 11 +++-
 .../testing/selftests/bpf/bpf_mptcp_helpers.h |  1 +
 .../testing/selftests/bpf/prog_tests/mptcp.c  | 38 ++++++++++++++
 .../selftests/bpf/progs/mptcp_bpf_red.c       | 52 +++++++++++++++++++
 7 files changed, 120 insertions(+), 13 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_red.c

-- 
2.34.1


             reply	other threads:[~2022-05-09 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 15:01 Geliang Tang [this message]
2022-05-09 15:01 ` [PATCH mptcp-next 1/4] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-05-11  0:18   ` Mat Martineau
2022-05-09 15:01 ` [PATCH mptcp-next 2/4] mptcp: add redundant subflows support Geliang Tang
2022-05-11  0:56   ` Mat Martineau
2022-05-09 15:01 ` [PATCH mptcp-next 3/4] selftests/bpf: add bpf_red scheduler Geliang Tang
2022-05-09 15:01 ` [PATCH mptcp-next 4/4] selftests/bpf: add bpf_red test Geliang Tang

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.1652108279.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