All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v3 0/3] Squash to "BPF packet scheduler"
Date: Fri, 6 Jun 2025 14:02:38 +0200	[thread overview]
Message-ID: <b5c707fa-4bf6-42db-b256-1ebaca4c95fb@kernel.org> (raw)
In-Reply-To: <cover.1748592117.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 30/05/2025 10:03, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> v3:
>  - put bpt_iter kfuncs into bpf_mptcp_iter_kfunc_set.

Thank you for this new version! The modifications in the code look good
to me, but applying them like that would cause issues in the code. Your
first squash-to patch for "bpf: Register mptcp common kfunc set" would
add a dependence on a later patch introducing bpf_mptcp_sched_ops.

I did the following modifications directly in the tree:
- Revert "bpf: Register mptcp common kfunc set".
- Add its content to "bpf: Add mptcp_subflow bpf_iter" & "bpf: Export
mptcp packet scheduler helpers".
- Remove the filter for the mptcp subflow iter.

Feel free to check the modifications I did and suggest any changes if
needed.

New patches for t/upstream:
- 7464c07e0b21: Revert "bpf: Register mptcp common kfunc set"
- 7a67a1f3a43d: tgupdate: merge t/bpf-Add-mptcp_subflow-bpf_iter base
into t/bpf-Add-mptcp_subflow-bpf_iter
- 6a9ee240a5f5: "squashed" (with conflicts) in "bpf: Add mptcp_subflow
bpf_iter"
- a3557639df4e: "squashed" (with conflicts) in "selftests/bpf: Add
mptcp_subflow bpf_iter subtest"
- 4bb0a3a3a05f: tgupdate: merge t/mptcp-add-bpf_mptcp_sched_ops base
into t/mptcp-add-bpf_mptcp_sched_ops
- e43d77b0c6aa: tgupdate: merge t/bpf-Add-bpf_mptcp_sched_kfunc_set base
into t/bpf-Add-bpf_mptcp_sched_kfunc_set
- 3f5d496d0334: conflict in t/selftests-bpf-Add-bpf-scheduler-test
- f89d0256f95f: conflict in t/selftests-bpf-add-bpf_first-scheduler
- Results: 226663e50465..8df73de5f995 (export)

Tests are now in progress:

- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/d4388fa1829e204dbc8bf97843787e8b143352cb/checks

Note: I will monitor the CI and hopefully fix new issues if any.

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


      parent reply	other threads:[~2025-06-06 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-30  8:03 [PATCH mptcp-next v3 0/3] Squash to "BPF packet scheduler" Geliang Tang
2025-05-30  8:03 ` [PATCH mptcp-next v3 1/3] Squash to "bpf: Register mptcp common kfunc set" Geliang Tang
2025-05-30  8:03 ` [PATCH mptcp-next v3 2/3] Squash to "bpf: Add mptcp_subflow bpf_iter" Geliang Tang
2025-06-06 12:02   ` Matthieu Baerts
2025-05-30  8:03 ` [PATCH mptcp-next v3 3/3] Revert "selftests/bpf: Add mptcp_subflow bpf_iter subtest" Geliang Tang
2025-05-30  9:28 ` [PATCH mptcp-next v3 0/3] Squash to "BPF packet scheduler" MPTCP CI
2025-06-06 12:02 ` Matthieu Baerts [this message]

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=b5c707fa-4bf6-42db-b256-1ebaca4c95fb@kernel.org \
    --to=matttbe@kernel.org \
    --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.