From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Subject: [PATCH mptcp-next 0/2] mptcp: sched: reduce size for unused data
Date: Fri, 21 Feb 2025 16:08:43 +0100 [thread overview]
Message-ID: <20250221-mptcp-sched-data-ptr-v1-0-dbaec476fa6b@kernel.org> (raw)
I was going to send "mptcp: sched: split get_subflow interface into two"
commit, when I saw again that the "data" structure was no longer used.
Because it will be removed later, when "use bpf_iter in bpf schedulers"
series will be applied, a first step is to save 64B from the stack for
each scheduling operation.
The first patch can be placed after "mptcp: sched: split get_subflow
interface into two", and the second one before or squashed into "mptcp:
add sched_data helpers": this commit can be dropped when "use bpf_iter
in bpf schedulers" series will be applied, no need to keep it for future
use. Same for the struct mptcp_sched_data.
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Matthieu Baerts (NGI0) (2):
mptcp: sched: reduce size for unused data
Squash to "mptcp: add sched_data helpers"
---
base-commit: 98f1e7131283309b4684ce977f28c9703d16b516
change-id: 20250221-mptcp-sched-data-ptr-8740fecdbbae
Best regards,
--
Matthieu Baerts (NGI0) <matttbe@kernel.org>
next reply other threads:[~2025-02-21 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:08 Matthieu Baerts (NGI0) [this message]
2025-02-21 15:08 ` [PATCH mptcp-next 1/2] mptcp: sched: reduce size for unused data Matthieu Baerts (NGI0)
2025-02-21 15:08 ` [PATCH mptcp-next 2/2] Squash to "mptcp: add sched_data helpers" Matthieu Baerts (NGI0)
2025-02-21 15:33 ` [PATCH mptcp-next 0/2] mptcp: sched: reduce size for unused data Matthieu Baerts
2025-02-21 15:56 ` Matthieu Baerts
2025-02-21 16:23 ` 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=20250221-mptcp-sched-data-ptr-v1-0-dbaec476fa6b@kernel.org \
--to=matttbe@kernel.org \
--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.