From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v2 0/6] BPF packet scheduler updates part 3
Date: Wed, 2 Aug 2023 19:55:26 +0800 [thread overview]
Message-ID: <cover.1690976940.git.geliang.tang@suse.com> (raw)
v2:
- use __always_inline instead of inline.
Some cleanups.
Geliang Tang (6):
Squash to "mptcp: add sched_data helpers"
Squash to "bpf: Add bpf_mptcp_sched_kfunc_set"
Squash to "selftests/bpf: add two mptcp netns helpers"
Squash to "bpf: Export more bpf_burst related functions"
Squash to "selftests/bpf: Add bpf_rr scheduler"
Squash to "selftests/bpf: Add bpf_burst scheduler"
net/mptcp/bpf.c | 10 ++++++++--
net/mptcp/protocol.h | 6 ------
net/mptcp/sched.c | 6 ++++++
tools/testing/selftests/bpf/bpf_tcp_helpers.h | 2 +-
tools/testing/selftests/bpf/prog_tests/mptcp.c | 1 -
tools/testing/selftests/bpf/progs/mptcp_bpf_burst.c | 2 +-
6 files changed, 16 insertions(+), 11 deletions(-)
--
2.35.3
next reply other threads:[~2023-08-02 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 11:55 Geliang Tang [this message]
2023-08-02 11:55 ` [PATCH mptcp-next v2 1/6] Squash to "mptcp: add sched_data helpers" Geliang Tang
2023-08-02 11:55 ` [PATCH mptcp-next v2 2/6] Squash to "bpf: Add bpf_mptcp_sched_kfunc_set" Geliang Tang
2023-08-02 11:55 ` [PATCH mptcp-next v2 3/6] Squash to "selftests/bpf: add two mptcp netns helpers" Geliang Tang
2023-08-02 11:55 ` [PATCH mptcp-next v2 4/6] Squash to "bpf: Export more bpf_burst related functions" Geliang Tang
2023-08-02 11:55 ` [PATCH mptcp-next v2 5/6] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2023-08-02 11:55 ` [PATCH mptcp-next v2 6/6] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-02 12:22 ` Squash to "selftests/bpf: Add bpf_burst scheduler": Build Failure MPTCP CI
2023-08-02 13:03 ` Squash to "selftests/bpf: Add bpf_burst scheduler": 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.1690976940.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;
as well as URLs for NNTP newsgroup(s).