All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Neal Cardwell <ncardwell@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	David Ahern <dsahern@kernel.org>, Shuah Khan <shuah@kernel.org>,
	netdev@vger.kernel.org, mptcp@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/8] mptcp: receive path improvement
Date: Wed, 1 Oct 2025 10:50:08 +0200	[thread overview]
Message-ID: <5ee6e86a-298b-41e9-971a-a40c1f96ec83@kernel.org> (raw)
In-Reply-To: <20250929182705.1583702f@kernel.org>

Hi Jakub,

On 30/09/2025 03:27, Jakub Kicinski wrote:
> On Sat, 27 Sep 2025 11:40:36 +0200 Matthieu Baerts (NGI0) wrote:
>> This series includes several changes to the MPTCP RX path. The main
>> goals are improving the RX performances, and increase the long term
>> maintainability.
>>
>> Some changes reflects recent(ish) improvements introduced in the TCP
>> stack: patch 1, 2 and 3 are the MPTCP counter part of SKB deferral free
>> and auto-tuning improvements. Note that patch 3 could possibly fix
>> additional issues, and overall such patch should protect from similar
>> issues to arise in the future.
>>
>> Patches 4-7 are aimed at introducing the socket backlog usage which will
>> be done in a later series to process the packets received by the
>> different subflows while the msk socket is owned.
>>
>> Patch 8 is not related to the RX path, but it contains additional tests
>> for new features recently introduced in net-next.
> 
> Could be a coincidence but we got 3 simult_flows.sh flakes since this
> was posted. Previous one was 20+ days ago:
> https://netdev.bots.linux.dev/contest.html?ld_cnt=250&pw-pass=n&pass=0&test=simult-flows-sh

Thank you for this message! Our CI didn't spot this issue in the last 2
weeks. I see it happened again on NIPA (sorry for that, and thank you
for having ignored this selftest) so I guess it is not a coincidence,
I'm going to investigate this issue ASAP.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2025-10-01  8:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-27  9:40 [PATCH net-next 0/8] mptcp: receive path improvement Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 1/8] mptcp: leverage skb deferral free Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 2/8] tcp: make tcp_rcvbuf_grow() accessible to mptcp code Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 3/8] mptcp: rcvbuf auto-tuning improvement Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 4/8] mptcp: introduce the mptcp_init_skb helper Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 5/8] mptcp: remove unneeded mptcp_move_skb() Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 6/8] mptcp: factor out a basic skb coalesce helper Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 7/8] mptcp: minor move_skbs_to_msk() cleanup Matthieu Baerts (NGI0)
2025-09-27  9:40 ` [PATCH net-next 8/8] selftests: mptcp: join: validate new laminar endp Matthieu Baerts (NGI0)
2025-09-30  1:27 ` [PATCH net-next 0/8] mptcp: receive path improvement Jakub Kicinski
2025-10-01  8:50   ` Matthieu Baerts [this message]
2025-09-30  1:30 ` patchwork-bot+netdevbpf

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=5ee6e86a-298b-41e9-971a-a40c1f96ec83@kernel.org \
    --to=matttbe@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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.