MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Shardul Bankar <shardul.b@mpiricsoftware.com>
Cc: MPTCP Linux <mptcp@lists.linux.dev>, janak@mpiric.us
Subject: Re: [PATCH mptcp-next 3/3] DO-NOT-MERGE: mptcp: sched: penalise counters
Date: Fri, 7 Aug 2026 18:10:04 +0200	[thread overview]
Message-ID: <9d846f7b-9c64-410d-a18e-933658f042c1@kernel.org> (raw)
In-Reply-To: <30b7b05258dda636068fd53b3e0b5a5ef509d3c1.camel@mpiricsoftware.com>

Hi Shardul,

Thank you for your reply!

On 07/08/2026 17:19, Shardul Bankar wrote:
> Hi Matt,
> 
> On Wed, 2026-07-29 at 13:50 +0200, Matthieu Baerts wrote:
>> Hi Shardul,
>>
>> On 26/07/2026 07:55, Shardul Bankar wrote:
>>> Instrumentation for validating the two preceding patches; not for
>>> merge.
>>>
>>> Adds two MPTcpExt SNMP counters:
>>> - CwndPenalized: times a subflow cwnd was actually halved;
>>> - PenalCandidate: times the rate trigger picked a slow subflow.
>>
>> I think at least the first counter is interesting, probably the
>> second
>> one as well, no?
>>
>> Generally, if you need counters during the development, they might be
>> needed to debug issues. But here with the scheduler, maybe the
>> tracing
>> are better. Did you use "trace_mptcp_subflow_get_send"?
>>
> 
> I did not. Looking at it now, it fires before the penalise decision and
> does not see the halving, so it would need a small extension (a new
> field, or a tracepoint at the halving point) to show what these
> counters show. Which would you prefer for v2: keep the DO-NOT-MERGE
> counters, or add that tracepoint? I will go with your call.

Maybe both?

If you can add a new field for the tracing, that would help with the
development. The MIB counter would help with the debugging.

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


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26  5:55 [PATCH mptcp-next 0/3] mptcp: sched: penalise a slow subflow (#345, first cut for your lab) Shardul Bankar
2026-07-26  5:55 ` [PATCH mptcp-next 1/3] mptcp: sched: penalise a slow subflow by halving its cwnd Shardul Bankar
2026-07-29 11:49   ` Matthieu Baerts
2026-08-07 15:18     ` Shardul Bankar
2026-08-07 16:10       ` Matthieu Baerts
2026-07-26  5:55 ` [PATCH mptcp-next 2/3] mptcp: sched: do not penalise when receive-window-limited Shardul Bankar
2026-07-29 11:49   ` Matthieu Baerts
2026-08-07 15:18     ` Shardul Bankar
2026-07-26  5:55 ` [PATCH mptcp-next 3/3] DO-NOT-MERGE: mptcp: sched: penalise counters Shardul Bankar
2026-07-29 11:50   ` Matthieu Baerts
2026-08-07 15:19     ` Shardul Bankar
2026-08-07 16:10       ` Matthieu Baerts [this message]
2026-07-26  7:14 ` [PATCH mptcp-next 0/3] mptcp: sched: penalise a slow subflow (#345, first cut for your lab) MPTCP CI
2026-07-29 11:48 ` Matthieu Baerts
2026-08-07 15:17   ` Shardul Bankar
2026-08-07 16:10     ` 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=9d846f7b-9c64-410d-a18e-933658f042c1@kernel.org \
    --to=matttbe@kernel.org \
    --cc=janak@mpiric.us \
    --cc=mptcp@lists.linux.dev \
    --cc=shardul.b@mpiricsoftware.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