All of lore.kernel.org
 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/7] BPF 'force to MPTCP'
Date: Wed,  5 Jul 2023 14:56:34 +0800	[thread overview]
Message-ID: <cover.1688540074.git.geliang.tang@suse.com> (raw)

v4:
 - add hooks in __sock_create().

v3:
 - add a wrapper socket_create(), the bpf hooks will added in this
   wrapper.

v2:
 - Address issue #79 "allow 'force to MPTCP' mode: BPF".
 - Define the prog in patch 3 in SEC "cgroup/sock_create" instead of
  "sockops".
 - Update other patches correspondingly.

v1:

This series depends on the two netns patches, should be inserted before
the BPF scheduler series:
  selftests/bpf: use random netns name for mptcp
  selftests/bpf: add two mptcp netns helpers
  bpf: Add bpf_mptcpify helper
  selftests/bpf: Test bpf_mptcpify helper
  selftests/bpf: Add mptcpify selftest
  mptcp: refactor push_pending logic

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/79

Geliang Tang (7):
  bpf: Add new prog type sockinit
  bpf: Run a sockinit program
  net: socket: run sockinit hooks
  libbpf: Support sockinit hook
  selftests/bpf: Add mptcpify program
  Squash to "selftests/bpf: add two mptcp netns helpers"
  selftests/bpf: Add mptcpify selftest

 include/linux/bpf-cgroup-defs.h               |   1 +
 include/linux/bpf-cgroup.h                    |  14 ++
 include/linux/bpf_types.h                     |   2 +
 include/uapi/linux/bpf.h                      |   8 ++
 kernel/bpf/cgroup.c                           |  90 +++++++++++++
 kernel/bpf/syscall.c                          |   7 +
 kernel/bpf/verifier.c                         |   1 +
 net/socket.c                                  |   6 +
 tools/include/uapi/linux/bpf.h                |   8 ++
 tools/lib/bpf/libbpf.c                        |   3 +
 tools/lib/bpf/libbpf_probes.c                 |   1 +
 .../bpf/cgroup_getset_retval_hooks.h          |   1 +
 .../testing/selftests/bpf/prog_tests/mptcp.c  | 124 +++++++++++++++---
 .../selftests/bpf/prog_tests/section_names.c  |   5 +
 tools/testing/selftests/bpf/progs/mptcpify.c  |  26 ++++
 15 files changed, 277 insertions(+), 20 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/progs/mptcpify.c

-- 
2.35.3


             reply	other threads:[~2023-07-05  6:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  6:56 Geliang Tang [this message]
2023-07-05  6:56 ` [PATCH mptcp-next v4 1/7] bpf: Add new prog type sockinit Geliang Tang
2023-07-05  6:56 ` [PATCH mptcp-next v4 2/7] bpf: Run a sockinit program Geliang Tang
2023-07-05  6:56 ` [PATCH mptcp-next v4 3/7] net: socket: run sockinit hooks Geliang Tang
2023-07-05  6:56 ` [PATCH mptcp-next v4 4/7] libbpf: Support sockinit hook Geliang Tang
2023-07-05  6:56 ` [PATCH mptcp-next v4 5/7] selftests/bpf: Add mptcpify program Geliang Tang
2023-07-05  6:56 ` [PATCH mptcp-next v4 6/7] Squash to "selftests/bpf: add two mptcp netns helpers" Geliang Tang
2023-07-05  8:04   ` Matthieu Baerts
2023-07-05  6:56 ` [PATCH mptcp-next v4 7/7] selftests/bpf: Add mptcpify selftest Geliang Tang
2023-07-05  8:15   ` selftests/bpf: Add mptcpify selftest: Tests Results MPTCP CI
2023-07-05  8:02 ` [PATCH mptcp-next v4 0/7] BPF 'force to MPTCP' Matthieu Baerts

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.1688540074.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.