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 00/14] save sched_data at mptcp_sock
Date: Mon,  5 Jun 2023 18:03:55 +0800	[thread overview]
Message-ID: <cover.1685959315.git.geliang.tang@suse.com> (raw)

v4:
 - drop "mptcp: add three helpers for bpf_burst", implement the helpers
   in the bpf context directly.

v3:
 - address Florian's comments in v2.
 - split into three more patches.

v2:
 - fix this error reported by CI:
KASAN: slab-use-after-free in __mptcp_close_ssk (net/mptcp/protocol.c:2461)
 - add bpf burst scheduler.

This patchset adds sched_data pointer into mptcp_sock to to save some
data at MPTCP and subflows levels.

With these changes, the old patch "mptcp: register default scheduler" in
[1] now works.

https://patchwork.kernel.org/project/mptcp/cover/cover.1665753926.git.geliang.tang@suse.com/ [1]
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/342

Geliang Tang (14):
  Squash to "mptcp: add struct mptcp_sched_ops"
  Squash to "mptcp: add sched in mptcp_sock"
  Squash to "mptcp: add scheduler wrappers"
  mptcp: add last_snd in sched_data
  mptcp: add snd_burst in sched_data
  mptcp: register default scheduler
  mptcp: rename __mptcp_set_timeout for bpf_burst
  mptcp: add two wrappers for bpf_burst
  Squash to "bpf: Add bpf_mptcp_sched_ops"
  Squash to "bpf: Add bpf_mptcp_sched_kfunc_set"
  Squash to "selftests/bpf: Add mptcp sched structs"
  Squash to "selftests/bpf: Add bpf_rr scheduler"
  selftests/bpf: Add bpf_burst scheduler
  selftests/bpf: Add bpf_burst test

 include/net/mptcp.h                           |   4 +-
 net/mptcp/bpf.c                               |  52 ++++-
 net/mptcp/protocol.c                          |  43 ++--
 net/mptcp/protocol.h                          |  12 +-
 net/mptcp/sched.c                             |  67 +++++-
 tools/testing/selftests/bpf/bpf_tcp_helpers.h |   9 +-
 .../testing/selftests/bpf/prog_tests/mptcp.c  |  38 ++++
 .../selftests/bpf/progs/mptcp_bpf_burst.c     | 213 ++++++++++++++++++
 .../selftests/bpf/progs/mptcp_bpf_rr.c        |   4 +-
 9 files changed, 391 insertions(+), 51 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_burst.c

-- 
2.35.3


             reply	other threads:[~2023-06-05 10:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 10:03 Geliang Tang [this message]
2023-06-05 10:03 ` [PATCH mptcp-next v4 01/14] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2023-06-05 10:03 ` [PATCH mptcp-next v4 02/14] Squash to "mptcp: add sched in mptcp_sock" Geliang Tang
2023-06-05 10:03 ` [PATCH mptcp-next v4 03/14] Squash to "mptcp: add scheduler wrappers" Geliang Tang
2023-06-05 10:03 ` [PATCH mptcp-next v4 04/14] mptcp: add last_snd in sched_data Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 05/14] mptcp: add snd_burst " Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 06/14] mptcp: register default scheduler Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 07/14] mptcp: rename __mptcp_set_timeout for bpf_burst Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 08/14] mptcp: add two wrappers " Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 09/14] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 10/14] Squash to "bpf: Add bpf_mptcp_sched_kfunc_set" Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 11/14] Squash to "selftests/bpf: Add mptcp sched structs" Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 12/14] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 13/14] selftests/bpf: Add bpf_burst scheduler Geliang Tang
2023-06-05 10:04 ` [PATCH mptcp-next v4 14/14] selftests/bpf: Add bpf_burst test Geliang Tang
2023-06-05 10:34   ` selftests/bpf: Add bpf_burst test: Build Failure MPTCP CI
2023-06-05 11:28   ` selftests/bpf: Add bpf_burst 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.1685959315.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