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 v10 00/12] BPF path manager, part 5
Date: Tue, 11 Mar 2025 00:16:56 +0100	[thread overview]
Message-ID: <6c8a2c9f-a426-4ec9-95f3-0479e1d37186@kernel.org> (raw)
In-Reply-To: <cover.1741258415.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 06/03/2025 12:01, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> v10:
>  - drop pm->init in mptcp_pm_validate, move mptcp_pm_validate into a new
>    patch.
>  - remove tlb, use ctl instead in proc_pm_type.
>  - use "strncmp() == 0" instead of "!strncmp()".
>  - set pm_type __MPTCP_PM_TYPE_NR for other names.
>  - add WARN_ON_ONCE in mptcp_pm_unregister.
>  - drop mptcp_userspace_pm_init.
>  - rename "struct mptcp_pm_ops *pm" to "struct mptcp_pm_ops *pm_ops".
>  - drop pm_ops NULL check in mptcp_pm_release.
>  - add struct_group for struct mptcp_pm_data.
>  - move selftests into userspace_pm.sh.

Thank you for the new version and the changelog!

I have some comments, almost there. If you already have patches adding
the remaining function pointers to the new mptcp_pm_ops, feel free to
add them in the next version.

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


      parent reply	other threads:[~2025-03-10 23:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 11:01 [PATCH mptcp-next v10 00/12] BPF path manager, part 5 Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 01/12] mptcp: pm: define struct mptcp_pm_ops Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 02/12] mptcp: pm: register in-kernel and userspace PM Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 03/12] mptcp: sysctl: set path manager by name Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 04/12] mptcp: add struct_group in mptcp_pm_data Geliang Tang
2025-03-10 23:17   ` Matthieu Baerts
2025-03-11  4:24     ` Geliang Tang
2025-03-11  8:53       ` Matthieu Baerts
2025-03-06 11:01 ` [PATCH mptcp-next v10 05/12] mptcp: pm: init and release mptcp_pm_ops Geliang Tang
2025-03-10 23:18   ` Matthieu Baerts
2025-03-06 11:01 ` [PATCH mptcp-next v10 06/12] mptcp: pm: add get_local_id() interface Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 07/12] mptcp: pm: add get_priority() interface Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 08/12] mptcp: pm: validate mandatory ops Geliang Tang
2025-03-10 23:18   ` Matthieu Baerts
2025-03-06 11:01 ` [PATCH mptcp-next v10 09/12] mptcp: sysctl: map path_manager to pm_type Geliang Tang
2025-03-10 23:19   ` Matthieu Baerts
2025-03-11  4:29     ` Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 10/12] mptcp: sysctl: map pm_type to path_manager Geliang Tang
2025-03-10 23:19   ` Matthieu Baerts
2025-03-06 11:01 ` [PATCH mptcp-next v10 11/12] mptcp: sysctl: add available_path_managers Geliang Tang
2025-03-06 11:01 ` [PATCH mptcp-next v10 12/12] selftests: mptcp: add path_manager sysctl tests Geliang Tang
2025-03-10 23:25   ` Matthieu Baerts
2025-03-11  6:54     ` Geliang Tang
2025-03-06 12:05 ` BPF path manager, part 5 MPTCP CI
2025-03-10 23:16 ` 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=6c8a2c9f-a426-4ec9-95f3-0479e1d37186@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.