From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v3 0/5] add bpf_stale scheduler
Date: Fri, 18 Aug 2023 15:58:28 +0800 [thread overview]
Message-ID: <cover.1692344463.git.geliang.tang@suse.com> (raw)
v3:
- init sk_storage in .init, delete it in .release.
We invoke bpf_sk_storage_get() to get the sk_storage map many times. Only
the first call is the slow path (see bpf_local_storage_lookup in
kernel/bpf/bpf_local_storage.c), alloc the map and cache it. The
subsequent calls are all in fast path, the cache hits. So we should
first call bpf_sk_storage_get in .init, then call it many times in
.get_subflow.
- if no subflow is scheduled, it should return '-1' to indicate an error.
v2:
- store subflow ids instead of storing subflow pointers in sk_storage.
v1:
- This patchset adds the new bpf_stale scheduler. Use sk_storage to save
the stale map instead of using subflow->stale flag to manage it.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/349
Geliang Tang (5):
Squash to "selftests/bpf: Add bpf_bkup scheduler"
Squash to "selftests/bpf: Add bpf_rr scheduler"
Squash to "selftests/bpf: Add bpf_burst scheduler"
selftests/bpf: Add bpf_stale scheduler
selftests/bpf: Add bpf_stale test
tools/testing/selftests/bpf/bpf_tcp_helpers.h | 1 +
.../testing/selftests/bpf/prog_tests/mptcp.c | 38 +++++
.../selftests/bpf/progs/mptcp_bpf_bkup.c | 4 +-
.../selftests/bpf/progs/mptcp_bpf_burst.c | 2 +
.../selftests/bpf/progs/mptcp_bpf_rr.c | 2 +
.../selftests/bpf/progs/mptcp_bpf_stale.c | 152 ++++++++++++++++++
6 files changed, 198 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/bpf/progs/mptcp_bpf_stale.c
--
2.35.3
next reply other threads:[~2023-08-18 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 7:58 Geliang Tang [this message]
2023-08-18 7:58 ` [PATCH mptcp-next v3 1/5] Squash to "selftests/bpf: Add bpf_bkup scheduler" Geliang Tang
2023-08-18 7:58 ` [PATCH mptcp-next v3 2/5] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2023-08-18 7:58 ` [PATCH mptcp-next v3 3/5] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-18 7:58 ` [PATCH mptcp-next v3 4/5] selftests/bpf: Add bpf_stale scheduler Geliang Tang
2023-09-01 23:23 ` Mat Martineau
2023-08-18 7:58 ` [PATCH mptcp-next v3 5/5] selftests/bpf: Add bpf_stale test Geliang Tang
2023-09-01 23:00 ` [PATCH mptcp-next v3 0/5] add bpf_stale scheduler Mat Martineau
2023-09-09 15:27 ` 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.1692344463.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.