All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH v2 mptcp-next 7/7] mptcp: implemented OoO queue pruning
Date: Sat, 8 Aug 2026 18:34:32 +0200	[thread overview]
Message-ID: <eb437699-4e3a-422d-93fa-3efde2985189@kernel.org> (raw)
In-Reply-To: <a8cf012f365d1885f773d5959829cb42298477bb.camel@kernel.org>

Hi Geliang, Paolo,

On 08/08/2026 04:31, Geliang Tang wrote:
> On Thu, 2026-08-06 at 18:46 +0200, Matthieu Baerts wrote:
>> On 06/08/2026 18:42, Paolo Abeni wrote:
>>> On 8/6/26 4:45 PM, Paolo Abeni wrote:
>>>> When moving incoming skbs in the msk receive queue and the latter
>>>> is above limits, prune it as needed quite alike what TCP is doing
>>>> at the subflow level. The main difference relies in the stop
>>>> condition:
>>>> since MPTCP does not perform collapsing, it's better off dropping
>>>> the
>>>> bare minimum to fit the (newer) incoming packet.

(...)

>>>> +/* The stack can't drop packets for fallback socket at the msk
>>>> level, or the
>>>> + * stream will break.
>>>> + */
>>>> +static bool mptcp_can_ingest(const struct sock *sk)
>>>> +{
>>>> +	return unlikely(sk_rmem_alloc_get(sk) <= READ_ONCE(sk-
>>>>> sk_rcvbuf)) ||
>>>> +			__mptcp_check_fallback(mptcp_sk(sk));
>>> The above should obviously be: 'likely(...)'
>>>
>>> @Matttbe: please LMK if you prefer a repost or you could adjust
>>> that
>>> while applying to the export branch.
>> No problem, I can adjust them when applying them (if there are no
>> other
>> big modifications required, but I guess no).
> 
> It seems you forgot to update this on the export branch.

Arf, indeed I did, my bad... good catch!

I just fixed it in our tree (and the alignment of the next line), but I
will wait for Paolo's feedback to know if he judges that a new version
is needed for upstream, or if that can be done in follow-up patches.

Maybe only the comments on the last patch actually requires
modifications? (but maybe can be done in a follow-up patch?)

https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260807-net-next-mptcp-oooq-pruning-v3-0-dbc1eb853cc3%40kernel.org

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


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 14:45 [PATCH v2 mptcp-next 0/7] mptcp: address stall under memory pressure Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 1/7] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 2/7] mptcp: move the stale logic out of retrans scheduler Paolo Abeni
2026-08-06 16:41   ` Paolo Abeni
2026-08-06 16:45     ` Matthieu Baerts
2026-08-06 14:45 ` [PATCH v2 mptcp-next 3/7] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 4/7] mptcp: explicitly drop over memory limits Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 5/7] mptcp: enforce hard limit on backlog flushing Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 6/7] mptcp: avoid code duplication in __mptcp_move_skb() Paolo Abeni
2026-08-06 14:45 ` [PATCH v2 mptcp-next 7/7] mptcp: implemented OoO queue pruning Paolo Abeni
2026-08-06 16:42   ` Paolo Abeni
2026-08-06 16:46     ` Matthieu Baerts
2026-08-08  2:31       ` Geliang Tang
2026-08-08 16:34         ` Matthieu Baerts [this message]
2026-08-10 10:47           ` Paolo Abeni
2026-08-07 11:45 ` [PATCH v2 mptcp-next 0/7] mptcp: address stall under memory pressure Matthieu Baerts

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=eb437699-4e3a-422d-93fa-3efde2985189@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --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 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.