From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next 0/2] remove bpf_mptcp_subflow_queues_empty
Date: Tue, 23 Jun 2026 10:56:10 +0800 [thread overview]
Message-ID: <cover.1782183266.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
This set removes bpf_mptcp_subflow_queues_empty() kfunc and updates
burst scheduler to implement tcp_rtx_queue_empty() inline.
Geliang Tang (2):
Squash to "bpf: Export mptcp packet scheduler helpers"
Squash to "selftests/bpf: Add bpf_burst scheduler & test"
net/mptcp/bpf.c | 6 ------
tools/testing/selftests/bpf/progs/mptcp_bpf.h | 1 +
tools/testing/selftests/bpf/progs/mptcp_bpf_burst.c | 9 +++++++--
3 files changed, 8 insertions(+), 8 deletions(-)
--
2.53.0
next reply other threads:[~2026-06-23 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 2:56 Geliang Tang [this message]
2026-06-23 2:56 ` [PATCH mptcp-next 1/2] Squash to "bpf: Export mptcp packet scheduler helpers" Geliang Tang
2026-06-23 2:56 ` [PATCH mptcp-next 2/2] Squash to "selftests/bpf: Add bpf_burst scheduler & test" Geliang Tang
2026-06-23 4:07 ` [PATCH mptcp-next 0/2] remove bpf_mptcp_subflow_queues_empty MPTCP CI
2026-06-23 9:03 ` 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.1782183266.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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