From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: geliang@kernel.org, Mat Martineau <martineau@kernel.org>,
mptcp@lists.linux.dev
Subject: Re: [PATCH v2 mptcp-net 2/2] mptcp: zero window probe mib
Date: Fri, 24 Oct 2025 10:07:06 +0200 [thread overview]
Message-ID: <fa1320f8-9512-46b3-9196-62e3404ae30c@kernel.org> (raw)
In-Reply-To: <14084e3b-2ee1-49bd-b04f-8281d4f9c3be@redhat.com>
Hi Paolo,
On 24/10/2025 09:30, Paolo Abeni wrote:
> On 10/23/25 6:26 PM, Matthieu Baerts wrote:
>> On 22/10/2025 09:39, Paolo Abeni wrote:
>>> Explicitly account for MPTCP-level zero windows probe, to catch
>>> hopefully earlier issues alike the one addressed by the previous
>>> patch.
>>>
>>> Reviewed-by: Mat Martineau <martineau@kernel.org>
>>> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
>>> ---
>>> net/mptcp/mib.c | 1 +
>>> net/mptcp/mib.h | 1 +
>>> net/mptcp/protocol.c | 1 +
>>> 3 files changed, 3 insertions(+)
>>>
>>> diff --git a/net/mptcp/mib.c b/net/mptcp/mib.c
>>> index 6003e47c770a7c..eb4645a9c5ac07 100644
>>> --- a/net/mptcp/mib.c
>>> +++ b/net/mptcp/mib.c
>>> @@ -85,6 +85,7 @@ static const struct snmp_mib mptcp_snmp_list[] = {
>>> SNMP_MIB_ITEM("DssFallback", MPTCP_MIB_DSSFALLBACK),
>>> SNMP_MIB_ITEM("SimultConnectFallback", MPTCP_MIB_SIMULTCONNFALLBACK),
>>> SNMP_MIB_ITEM("FallbackFailed", MPTCP_MIB_FALLBACKFAILED),
>>> + SNMP_MIB_ITEM("MPTcpWinProbe", MPTCP_MIB_MPTCPWINPROBE),
>>
>> Detail: I just noticed that after having applied the patch: Do we need
>> to double the 'MPTCP' keyword here? The full MIB counter name is:
>>
>> MPTcpExtMPTcpWinProbe
>>
>> Maybe just WinProbe is enough? → MPTcpExtWinProbe
>
> I'm sorry for the late reply. Yes WinProbe -> MPTcpExtWinProbe is the
> correct/intended name, if you could fix that in the tree would be great,
> thanks!
Thanks! Just did! I also renamed the enum
MPTCP_MIB_MPTCPWINPROBE → MPTCP_MIB_WINPROBE:
New patches for t/upstream-net and t/upstream:
- 9525948cb5cc: Squash to "mptcp: zero window probe mib"
- Results: f6c0967d41d1..628a66ff3d17 (export-net)
- Results: 8416614a1e27..6354d0b32825 (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/60ce52cf453b5182b993d2420d01422355ebbd67/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/a76c4725014b6c51385d301f1027a7891714a6bb/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-10-24 8:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 7:39 [PATCH v2 mptcp-net 0/2] mptcp: restore zero window probe Paolo Abeni
2025-10-22 7:39 ` [PATCH v2 mptcp-net 1/2] mptcp: restore " Paolo Abeni
2025-10-22 7:39 ` [PATCH v2 mptcp-net 2/2] mptcp: zero window probe mib Paolo Abeni
2025-10-23 16:26 ` Matthieu Baerts
2025-10-24 7:30 ` Paolo Abeni
2025-10-24 8:07 ` Matthieu Baerts [this message]
2025-10-22 8:55 ` [PATCH v2 mptcp-net 0/2] mptcp: restore zero window probe MPTCP CI
2025-10-22 10:07 ` Geliang Tang
2025-10-23 6:24 ` Geliang Tang
2025-10-23 15:54 ` Matthieu Baerts
2025-10-24 9:03 ` Geliang Tang
2025-10-23 16:23 ` 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=fa1320f8-9512-46b3-9196-62e3404ae30c@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=martineau@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