All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next 0/2] Drop mptcp_pm_subflow_chk_stale in bpf
Date: Thu, 6 Aug 2026 18:54:37 +0200	[thread overview]
Message-ID: <5f3c924f-6099-4d58-8332-df27e6a6b728@redhat.com> (raw)
In-Reply-To: <cover.1786007209.git.tanggeliang@kylinos.cn>

On 8/6/26 11:10 AM, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> Since mptcp_pm_subflow_chk_stale is removed in the "mptcp: address stall
> under memory pressure" series, this patch drops it from BPF to keep the
> BPF tests passing.
> 
> Based-on: <cover.1785943854.git.pabeni@redhat.com>
> 
> Geliang Tang (2):
>   Squash to "bpf: Export mptcp packet scheduler helpers"
>   Squash to "selftests/bpf: Add bpf_burst scheduler & test"
> 
>  net/mptcp/bpf.c                                     | 1 -
>  tools/testing/selftests/bpf/progs/mptcp_bpf_burst.c | 2 --
>  2 files changed, 3 deletions(-)
> 

Thanks Geliang for the quick turn around!

Both patches LGTM!

Side note: I really think it's for the better to keep the stale subflow
logic detection out of the retrans scheduler.

/P


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  9:10 [PATCH mptcp-next 0/2] Drop mptcp_pm_subflow_chk_stale in bpf Geliang Tang
2026-08-06  9:10 ` [PATCH mptcp-next 1/2] Squash to "bpf: Export mptcp packet scheduler helpers" Geliang Tang
2026-08-06  9:10 ` [PATCH mptcp-next 2/2] Squash to "selftests/bpf: Add bpf_burst scheduler & test" Geliang Tang
2026-08-06 10:17 ` [PATCH mptcp-next 0/2] Drop mptcp_pm_subflow_chk_stale in bpf MPTCP CI
2026-08-06 16:54 ` Paolo Abeni [this message]
2026-08-07 11:46 ` 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=5f3c924f-6099-4d58-8332-df27e6a6b728@redhat.com \
    --to=pabeni@redhat.com \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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.