From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, kuniyu@amazon.com,
willemb@google.com, dsahern@kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] mptcp: rx path refactor
Date: Thu, 20 Feb 2025 03:10:43 +0000 [thread overview]
Message-ID: <174002104323.825980.13872067512718891782.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250218-net-next-mptcp-rx-path-refactor-v1-0-4a47d90d7998@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Feb 2025 19:36:11 +0100 you wrote:
> Paolo worked on this RX path refactor for these two main reasons:
>
> - Currently, the MPTCP RX path introduces quite a bit of 'exceptional'
> accounting/locking processing WRT to plain TCP, adding up to the
> implementation complexity in a miserable way.
>
> - The performance gap WRT plain TCP for single subflow connections is
> quite measurable.
>
> [...]
Here is the summary with links:
- [net-next,1/7] mptcp: consolidate subflow cleanup
https://git.kernel.org/netdev/net-next/c/c3349a22c200
- [net-next,2/7] mptcp: drop __mptcp_fastopen_gen_msk_ackseq()
https://git.kernel.org/netdev/net-next/c/f03afb3aeb9d
- [net-next,3/7] mptcp: move the whole rx path under msk socket lock protection
https://git.kernel.org/netdev/net-next/c/bc68b0efa1bf
- [net-next,4/7] mptcp: cleanup mem accounting
https://git.kernel.org/netdev/net-next/c/6639498ed85f
- [net-next,5/7] net: dismiss sk_forward_alloc_get()
https://git.kernel.org/netdev/net-next/c/c8802ded4658
- [net-next,6/7] mptcp: dismiss __mptcp_rmem()
https://git.kernel.org/netdev/net-next/c/51fe9cb9213e
- [net-next,7/7] mptcp: micro-optimize __mptcp_move_skb()
https://git.kernel.org/netdev/net-next/c/e0ca4057e0ec
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:[~2025-02-20 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 18:36 [PATCH net-next 0/7] mptcp: rx path refactor Matthieu Baerts (NGI0)
2025-02-18 18:36 ` [PATCH net-next 1/7] mptcp: consolidate subflow cleanup Matthieu Baerts (NGI0)
2025-02-18 18:36 ` [PATCH net-next 2/7] mptcp: drop __mptcp_fastopen_gen_msk_ackseq() Matthieu Baerts (NGI0)
2025-02-18 18:36 ` [PATCH net-next 3/7] mptcp: move the whole rx path under msk socket lock protection Matthieu Baerts (NGI0)
2025-02-18 18:36 ` [PATCH net-next 4/7] mptcp: cleanup mem accounting Matthieu Baerts (NGI0)
2025-02-18 18:36 ` [PATCH net-next 5/7] net: dismiss sk_forward_alloc_get() Matthieu Baerts (NGI0)
2025-02-18 18:36 ` [PATCH net-next 6/7] mptcp: dismiss __mptcp_rmem() Matthieu Baerts (NGI0)
2025-02-18 18:36 ` [PATCH net-next 7/7] mptcp: micro-optimize __mptcp_move_skb() Matthieu Baerts (NGI0)
2025-02-20 3:10 ` 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=174002104323.825980.13872067512718891782.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=xiyou.wangcong@gmail.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