From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [RFC mptcp-next v2 0/2] BPF packet scheduler updates part 4
Date: Wed, 23 Aug 2023 19:04:44 +0800 [thread overview]
Message-ID: <cover.1692788531.git.geliang.tang@suse.com> (raw)
v2:
- keep sched API unchanged.
- use bpf_sk_storage_lookup to get snd_burst from BPF context.
- applied after "add bpf_stale scheduler v3" serise.
v1:
There's a bug in bpf_burst. snd_burst stored in mptcp_burst_storage in
BPF context is not used. msk->snd_burst is still used in kernel space.
To fix this, add two new interfaces in mptcp_sched_ops to get and set
scheduler's paramters from BPF context to kernel space.
Geliang Tang (2):
mptcp: add set/get params wrappers
mptcp: add bpf_burst set/get params
include/net/bpf_sk_storage.h | 7 +++++
net/core/bpf_sk_storage.c | 2 +-
net/mptcp/protocol.c | 8 ++---
net/mptcp/protocol.h | 2 ++
net/mptcp/sched.c | 57 ++++++++++++++++++++++++++++++++++++
5 files changed, 71 insertions(+), 5 deletions(-)
--
2.35.3
next reply other threads:[~2023-08-23 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 11:04 Geliang Tang [this message]
2023-08-23 11:04 ` [RFC mptcp-next v2 1/2] mptcp: add set/get params wrappers Geliang Tang
2023-08-23 11:04 ` [RFC mptcp-next v2 2/2] mptcp: add bpf_burst set/get params Geliang Tang
2023-08-23 11:28 ` mptcp: add bpf_burst set/get params: Build Failure MPTCP CI
2023-08-23 12:11 ` mptcp: add bpf_burst set/get params: Tests Results MPTCP CI
2023-08-23 17:21 ` [RFC mptcp-next v2 2/2] mptcp: add bpf_burst set/get params kernel test robot
2023-08-23 17:21 ` kernel test robot
2023-08-23 20:09 ` kernel test robot
2023-08-23 21:12 ` kernel test robot
2023-08-26 1:21 ` kernel test robot
2023-08-26 1:44 ` kernel test robot
2023-09-01 23:53 ` Mat Martineau
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.1692788531.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.