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 5/9] mptcp: drop free_list for deleting entries
Date: Wed, 4 Dec 2024 18:49:01 +0100	[thread overview]
Message-ID: <0df84759-abb5-4030-bb2b-1e73ab2b8693@kernel.org> (raw)
In-Reply-To: <68e7a3deaea7319b4fb36b9ee8a6073a8bbfa37d.1730961810.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 07/11/2024 07:45, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> mptcp_pm_remove_addrs() actually only deletes one address, which does
> not match its name. This patch renames it to mptcp_pm_remove_addr_entry()
> and changes the parameter "rm_list" to "entry".
> 
> With the help of mptcp_pm_remove_addr_entry(), it's no longer necessary to
> move the entry to be deleted to free_list and then traverse the list to
> delete the entry, which is not allowed in BPF. The entry can be directly
> deleted through list_del_rcu() and sock_kfree_s() now.
> 
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
>  net/mptcp/pm_userspace.c | 33 ++++++++++++---------------------
>  net/mptcp/protocol.h     |  3 ++-
>  2 files changed, 14 insertions(+), 22 deletions(-)
> 
> diff --git a/net/mptcp/pm_userspace.c b/net/mptcp/pm_userspace.c
> index 737a07f5defe..a98da9a44bfa 100644
> --- a/net/mptcp/pm_userspace.c
> +++ b/net/mptcp/pm_userspace.c
> @@ -286,26 +286,21 @@ static int mptcp_userspace_pm_remove_id_zero_address(struct mptcp_sock *msk,
>  	return err;
>  }
>  
> -void mptcp_pm_remove_addrs(struct mptcp_sock *msk, struct list_head *rm_list)
> +void mptcp_pm_remove_addr_entry(struct mptcp_sock *msk,
> +				struct mptcp_pm_addr_entry *entry)
>  {
>  	struct mptcp_rm_list alist = { .nr = 0 };
> -	struct mptcp_pm_addr_entry *entry;
>  	int anno_nr = 0;
>  
> -	list_for_each_entry(entry, rm_list, list) {
> -		if (alist.nr >= MPTCP_RM_IDS_MAX)
> -			break;
> -
> -		/* only delete if either announced or matching a subflow */
> -		if (mptcp_remove_anno_list_by_saddr(msk, &entry->addr))
> -			anno_nr++;
> -		else if (!mptcp_lookup_subflow_by_saddr(&msk->conn_list,
> -							&entry->addr))
> -			continue;
> +	/* only delete if either announced or matching a subflow */
> +	if (mptcp_remove_anno_list_by_saddr(msk, &entry->addr))
> +		anno_nr++;
> +	else if (!mptcp_lookup_subflow_by_saddr(&msk->conn_list, &entry->addr))
> +		goto out;

Here, you can 'return', no need to use this new 'out' label.

>  
> -		alist.ids[alist.nr++] = entry->addr.id;
> -	}
> +	alist.ids[alist.nr++] = entry->addr.id;
>  
> +out:
>  	if (alist.nr) {

If the 'out' label is removed, you can also remove this if-statement.

>  		spin_lock_bh(&msk->pm.lock);
>  		msk->pm.add_addr_signaled -= anno_nr;

(...)

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


  reply	other threads:[~2024-12-04 17:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  6:45 [PATCH mptcp-next v3 0/9] BPF path manager, part 1 Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 1/9] mptcp: add mptcp_userspace_pm_lookup_addr helper Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 2/9] mptcp: add mptcp_for_each_userspace_pm_addr macro Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 3/9] mptcp: add mptcp_userspace_pm_get_sock helper Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 4/9] mptcp: move mptcp_pm_remove_addrs into pm_userspace Geliang Tang
2024-12-04 17:48   ` Matthieu Baerts
2024-12-05  7:26     ` Geliang Tang
2024-12-05  9:27       ` Matthieu Baerts
2024-12-05  9:36         ` Geliang Tang
2024-12-05  9:38           ` Matthieu Baerts
2024-11-07  6:45 ` [PATCH mptcp-next v3 5/9] mptcp: drop free_list for deleting entries Geliang Tang
2024-12-04 17:49   ` Matthieu Baerts [this message]
2024-12-05  7:27     ` Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 6/9] mptcp: use mptcp_pm_local in pm_netlink only Geliang Tang
2024-11-10  4:40   ` Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 7/9] mptcp: drop struct mptcp_pm_add_entry Geliang Tang
2024-12-04 17:49   ` Matthieu Baerts
2024-12-05  7:28     ` Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 8/9] mptcp: change local addr type of subflow_destroy Geliang Tang
2024-11-07  6:45 ` [PATCH mptcp-next v3 9/9] mptcp: drop useless "err = 0" in subflow_destroy Geliang Tang
2024-12-04 17:49   ` Matthieu Baerts
2024-12-05  7:30     ` Geliang Tang
2024-11-07  7:56 ` [PATCH mptcp-next v3 0/9] BPF path manager, part 1 MPTCP CI
2024-12-04 17:48 ` 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=0df84759-abb5-4030-bb2b-1e73ab2b8693@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.