All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: ethernet: mediatek: mtk_ppe: prefer newly added l2 flows over existing ones
Date: Wed, 22 Mar 2023 15:00:55 +0100	[thread overview]
Message-ID: <ZBsKF4r7bARMFNp0@corigine.com> (raw)
In-Reply-To: <20230321133609.49591-2-nbd@nbd.name>

On Tue, Mar 21, 2023 at 02:36:09PM +0100, Felix Fietkau wrote:
> When a device is roaming between interfaces and a new flow entry is created,
> we should assume that its output device is more up to date than whatever
> entry existed already.

As per patch 1/2. checkpatch complains that the patch description
has lines more than 75 characters long.

That aside, this change looks good to me.
But I'm wondering if it is fixing a bug.
Or just improving something suboptimal (form a user experience POV).

> 
> Signed-off-by: Felix Fietkau <nbd@nbd.name>

> ---
>  drivers/net/ethernet/mediatek/mtk_ppe.c | 14 ++++++++++++--
>  1 file changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/ethernet/mediatek/mtk_ppe.c b/drivers/net/ethernet/mediatek/mtk_ppe.c
> index 6883eb34cd8b..5e150007bb7d 100644
> --- a/drivers/net/ethernet/mediatek/mtk_ppe.c
> +++ b/drivers/net/ethernet/mediatek/mtk_ppe.c
> @@ -580,10 +580,20 @@ void mtk_foe_entry_clear(struct mtk_ppe *ppe, struct mtk_flow_entry *entry)
>  static int
>  mtk_foe_entry_commit_l2(struct mtk_ppe *ppe, struct mtk_flow_entry *entry)
>  {
> +	struct mtk_flow_entry *prev;
> +
>  	entry->type = MTK_FLOW_TYPE_L2;
>  
> -	return rhashtable_insert_fast(&ppe->l2_flows, &entry->l2_node,
> -				      mtk_flow_l2_ht_params);
> +	prev = rhashtable_lookup_get_insert_fast(&ppe->l2_flows, &entry->l2_node,
> +						 mtk_flow_l2_ht_params);
> +	if (likely(!prev))
> +		return 0;
> +
> +	if (IS_ERR(prev))
> +		return PTR_ERR(prev);
> +
> +	return rhashtable_replace_fast(&ppe->l2_flows, &prev->l2_node,
> +				       &entry->l2_node, mtk_flow_l2_ht_params);
>  }
>  
>  int mtk_foe_entry_commit(struct mtk_ppe *ppe, struct mtk_flow_entry *entry)
> -- 
> 2.39.0
> 

  reply	other threads:[~2023-03-22 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 13:36 [PATCH net-next 1/2] net: ethernet: mtk_eth_soc: add code for offloading flows from wlan devices Felix Fietkau
2023-03-21 13:36 ` [PATCH net-next 2/2] net: ethernet: mediatek: mtk_ppe: prefer newly added l2 flows over existing ones Felix Fietkau
2023-03-22 14:00   ` Simon Horman [this message]
2023-03-22 15:09     ` Felix Fietkau
2023-03-22 20:00       ` Simon Horman
2023-03-22 14:04 ` [PATCH net-next 1/2] net: ethernet: mtk_eth_soc: add code for offloading flows from wlan devices Simon Horman
2023-03-22 14:29   ` Simon Horman
2023-03-22 15:19     ` Felix Fietkau
2023-03-22 20:05       ` Simon Horman
2023-03-22 15:18   ` Felix Fietkau
2023-03-22 20:04     ` Simon Horman

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=ZBsKF4r7bARMFNp0@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    /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.