From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH v10 mptcp-next 1/3] Squash-to: "mptcp: implemented OoO queue pruning"
Date: Sat, 30 May 2026 18:52:05 +1000 [thread overview]
Message-ID: <d7d6789f-101e-4dac-a4a9-5cc90fa55ab5@kernel.org> (raw)
In-Reply-To: <34aad036969501b2e71025a68bd3925e478bc3c8.1780049797.git.pabeni@redhat.com>
Hi Paolo,
On 29/05/2026 20:44, Paolo Abeni wrote:
> As discussed in the original patch, use the proper helper to
> get the currently used memory, and let mptcp_prune_ofo_queue()
> return true when skb can be accepted, to avoid code churn in
> the caller.
I just applied this patch 1/3, but not 2-3/3.
New patches for t/upstream:
- cba0bf051b53: Squash-to: "mptcp: implemented OoO queue pruning"
- Results: 4d6bda29d05f..24c473fa6c91 (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/9d89b8f76d6640109b7e412a3710c62c67000ac1/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-05-30 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 10:44 [PATCH v10 mptcp-next 0/3] mptcp: address stall under memory pressure Paolo Abeni
2026-05-29 10:44 ` [PATCH v10 mptcp-next 1/3] Squash-to: "mptcp: implemented OoO queue pruning" Paolo Abeni
2026-05-30 8:52 ` Matthieu Baerts [this message]
2026-05-29 10:44 ` [PATCH v10 mptcp-next 2/3] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-05-29 10:44 ` [PATCH v10 mptcp-next 3/3] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-05-29 13:27 ` Geliang Tang
2026-05-29 14:14 ` Paolo Abeni
2026-05-29 14:41 ` Paolo Abeni
2026-05-29 17:04 ` Paolo Abeni
2026-05-30 4:23 ` Geliang Tang
2026-05-29 12:00 ` [PATCH v10 mptcp-next 0/3] mptcp: address stall under memory pressure MPTCP CI
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=d7d6789f-101e-4dac-a4a9-5cc90fa55ab5@kernel.org \
--to=matttbe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox