From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 0/2] mptcp: sched: reduce size for unused data
Date: Fri, 21 Feb 2025 16:33:48 +0100 [thread overview]
Message-ID: <61a4b545-dc93-4be3-859f-b79d018e758a@kernel.org> (raw)
In-Reply-To: <20250221-mptcp-sched-data-ptr-v1-0-dbaec476fa6b@kernel.org>
Hello,
On 21/02/2025 16:08, Matthieu Baerts (NGI0) wrote:
> 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.
I suggest applying this now, not to block the other patch: this small
modification is trivial, and undo only in our tree.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-02-21 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 15:08 [PATCH mptcp-next 0/2] mptcp: sched: reduce size for unused data Matthieu Baerts (NGI0)
2025-02-21 15:08 ` [PATCH mptcp-next 1/2] " 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 ` Matthieu Baerts [this message]
2025-02-21 15:56 ` [PATCH mptcp-next 0/2] mptcp: sched: reduce size for unused data 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=61a4b545-dc93-4be3-859f-b79d018e758a@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.