MPTCP Linux Development
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 2/7] mptcp: move the stale logic out of retrans scheduler
Date: Thu, 6 Aug 2026 18:57:04 +0200	[thread overview]
Message-ID: <47fa3b88-6534-41a0-ac93-81ed87f2f5e4@redhat.com> (raw)
In-Reply-To: <8a3758427e722a547c1a173dff8149c4cd33a479.camel@kernel.org>

On 8/6/26 11:31 AM, Geliang Tang wrote:
> Thank you for this new version of the series. I have rebased the MPTCP
> KTLS code onto it, and all tests passed.
> 
> On Wed, 2026-08-05 at 18:17 +0200, Paolo Abeni wrote:
>> This allow separating the stale logic invocation and the retrans
>> scheduler, and will simplify the next patch.
>>
>> It's also a cleaner design as the retrans scheduler has currently
>> too many side effects. As a possible downside, the retrans work will
>> now traverse the subflows list additional times; that does not matter
>> much, as this is slowpath.
> 
> However, this patch makes the KTLS selftests significantly slower -
> specifically, this test case now takes several hundred seconds to
> complete, whereas it previously finished in just a few seconds:
> 
> 	chunked_sendfile(_metadata, self, 1, 4096);
> 
> Is there any way we can make it run faster?
I guess you test on top of the whole series?

If you tested on top of the whole series, I think the slowdown is due to
the issue in patch 3/7 noted by sashiko gemini and should be fixed in v2.

/P


  reply	other threads:[~2026-08-06 16:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 15:52 [PATCH mptcp-next 0/7] mptcp: address stall under memory pressure Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 1/7] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 2/7] mptcp: move the stale logic out of retrans scheduler Paolo Abeni
2026-08-06  9:31   ` Geliang Tang
2026-08-06 16:57     ` Paolo Abeni [this message]
2026-08-05 16:17 ` [PATCH mptcp-next 3/7] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-08-06  7:39   ` Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 4/7] mptcp: explicitly drop over memory limits Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 5/7] mptcp: enforce hard limit on backlog flushing Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 6/7] mptcp: avoid code duplication in __mptcp_move_skb() Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 7/7] mptcp: implemented OoO queue pruning Paolo Abeni
2026-08-05 17:30 ` [PATCH mptcp-next 0/7] mptcp: address stall under memory pressure MPTCP CI
2026-08-06  9:16   ` Geliang Tang

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=47fa3b88-6534-41a0-ac93-81ed87f2f5e4@redhat.com \
    --to=pabeni@redhat.com \
    --cc=geliang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox