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 v4 0/5] BPF redundant scheduler
Date: Mon,  6 Jun 2022 17:47:10 +0800	[thread overview]
Message-ID: <cover.1654508532.git.geliang.tang@suse.com> (raw)

v4:
 - small cleanups in patch 1, 2.
 - add TODO in patch 3.
 - rebase patch 5 on 'cleanups for bpf sched selftests'.

v3:
 - use new API.
 - fix the link failure tests issue mentioned in ("https://patchwork.kernel.org/project/mptcp/cover/cover.1653033459.git.geliang.tang@suse.com/").

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.

Geliang Tang (5):
  Squash to "mptcp: add get_subflow wrappers"
  mptcp: add __mptcp_sched_get_retrans wrapper
  mptcp: add mptcp_sched_get_send wrapper
  selftests/bpf: Add bpf_red scheduler
  selftests/bpf: Add bpf_red test

 net/mptcp/protocol.c                          | 108 ++++++++++--------
 net/mptcp/protocol.h                          |   3 +-
 net/mptcp/sched.c                             |  70 ++++++++----
 net/mptcp/subflow.c                           |   1 -
 .../testing/selftests/bpf/prog_tests/mptcp.c  |  34 ++++++
 .../selftests/bpf/progs/mptcp_bpf_red.c       |  36 ++++++
 6 files changed, 180 insertions(+), 72 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_red.c

-- 
2.34.1


             reply	other threads:[~2022-06-06  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06  9:47 Geliang Tang [this message]
2022-06-06  9:47 ` [PATCH mptcp-next v4 1/5] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-06-06  9:47 ` [PATCH mptcp-next v4 2/5] mptcp: add __mptcp_sched_get_retrans wrapper Geliang Tang
2022-06-06  9:47 ` [PATCH mptcp-next v4 3/5] mptcp: add mptcp_sched_get_send wrapper Geliang Tang
2022-06-06 11:11   ` Paolo Abeni
2022-06-06  9:47 ` [PATCH mptcp-next v4 4/5] selftests/bpf: Add bpf_red scheduler Geliang Tang
2022-06-06  9:47 ` [PATCH mptcp-next v4 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-06-06 11:47   ` 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.1654508532.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