From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <martineau@kernel.org>
Cc: matthieu.baerts@tessares.net, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
geliang.tang@suse.com
Subject: Re: [PATCH net-next 00/10] mptcp: Prepare MPTCP packet scheduler for BPF extension
Date: Wed, 23 Aug 2023 01:40:25 +0000 [thread overview]
Message-ID: <169275482578.27929.1775415054097183843.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230821-upstream-net-next-20230818-v1-0-0c860fb256a8@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Aug 2023 15:25:11 -0700 you wrote:
> The kernel's MPTCP packet scheduler has, to date, been a one-size-fits
> all algorithm that is hard-coded. It attempts to balance latency and
> throughput when transmitting data across multiple TCP subflows, and has
> some limited tunability through sysctls. It has been a long-term goal of
> the Linux MPTCP community to support customizable packet schedulers for
> use cases that need to make different trade-offs regarding latency,
> throughput, redundancy, and other metrics. BPF is well-suited for
> configuring customized, per-packet scheduling decisions without having
> to modify the kernel or manage out-of-tree kernel modules.
>
> [...]
Here is the summary with links:
- [net-next,01/10] mptcp: refactor push_pending logic
https://git.kernel.org/netdev/net-next/c/c5b4297dee91
- [net-next,02/10] mptcp: drop last_snd and MPTCP_RESET_SCHEDULER
https://git.kernel.org/netdev/net-next/c/ebc1e08f01eb
- [net-next,03/10] mptcp: add struct mptcp_sched_ops
https://git.kernel.org/netdev/net-next/c/740ebe35bd3f
- [net-next,04/10] mptcp: add a new sysctl scheduler
https://git.kernel.org/netdev/net-next/c/e3b2870b6d22
- [net-next,05/10] mptcp: add sched in mptcp_sock
https://git.kernel.org/netdev/net-next/c/1730b2b2c5a5
- [net-next,06/10] mptcp: add scheduled in mptcp_subflow_context
https://git.kernel.org/netdev/net-next/c/fce68b03086f
- [net-next,07/10] mptcp: add scheduler wrappers
https://git.kernel.org/netdev/net-next/c/07336a87fe87
- [net-next,08/10] mptcp: use get_send wrapper
https://git.kernel.org/netdev/net-next/c/0fa1b3783a17
- [net-next,09/10] mptcp: use get_retrans wrapper
https://git.kernel.org/netdev/net-next/c/ee2708aedad0
- [net-next,10/10] mptcp: register default scheduler
https://git.kernel.org/netdev/net-next/c/ed1ad86b8527
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-23 1:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 22:25 [PATCH net-next 00/10] mptcp: Prepare MPTCP packet scheduler for BPF extension Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 01/10] mptcp: refactor push_pending logic Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 02/10] mptcp: drop last_snd and MPTCP_RESET_SCHEDULER Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 03/10] mptcp: add struct mptcp_sched_ops Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 04/10] mptcp: add a new sysctl scheduler Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 05/10] mptcp: add sched in mptcp_sock Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 06/10] mptcp: add scheduled in mptcp_subflow_context Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 07/10] mptcp: add scheduler wrappers Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 08/10] mptcp: use get_send wrapper Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 09/10] mptcp: use get_retrans wrapper Mat Martineau
2023-08-21 22:25 ` [PATCH net-next 10/10] mptcp: register default scheduler Mat Martineau
2023-08-23 1:40 ` patchwork-bot+netdevbpf [this message]
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=169275482578.27929.1775415054097183843.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang.tang@suse.com \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).