Received-SPF: pass (google.com: domain of linux-kernel+bounces-54230-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
References: <20240206024956.226452-1-jdamato@fastly.com>
User-agent: mu4e 1.10.8; emacs 28.2
From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Joe Damato <jdamato@fastly.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, tariqt@nvidia.com,
 Saeed Mahameed <saeedm@nvidia.com>, Leon Romanovsky <leon@kernel.org>,
 "David S. Miller" <davem@davemloft.net>, Eric Dumazet
 <edumazet@google.com>, Jakub Kicinski <kuba@kernel.org>, Paolo Abeni
 <pabeni@redhat.com>, "open list:MELLANOX MLX5 core VPI driver"
 <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH net-next v2] eth: mlx5: link NAPI instances to queues
 and IRQs
Date: Mon, 05 Feb 2024 18:52:45 -0800
In-reply-to: <20240206024956.226452-1-jdamato@fastly.com>
Message-ID: <87o7cul2nf.fsf@nvidia.com>
Content-Type: text/plain
Precedence: bulk
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0:
	=?us-ascii?Q?6schq388WSemHouyHwoOVJeKXZngJ6tbL1rYW1fVNxaboLxBKWP/4C1QP69t?=
 =?us-ascii?Q?JhGIM4yfDEw9DASKtEIJoNrHOc+mT0veRpJj3mbjVAbDx6LWne/jS+3ujgd/?=
 =?us-ascii?Q?xqO/7cREqP0GGYiM6VcOZVvs9O1eiWiT3PNbiRdc0TPqLcdwou5t0mUhtP2g?=
 =?us-ascii?Q?b8cDeb3FyRfoHxmmDLZznj13GR2iaiDXKCLveF2q1+0Tk0oJeETTuyKAz2z6?=
 =?us-ascii?Q?2Zx8tCLJUsI4Lrd/8IjkCepuaUoaThojbsU0k37PLmLUcI9P6rryliRRO62K?=
 =?us-ascii?Q?1vJ7HY3QfOMIOfwnrd0eQDYqatOmxaN7YJvyvCnO2edTMTpDA2iuhQkwTh7N?=
 =?us-ascii?Q?X/7kj81eFrk2UT5AeEhMsvT5gYtD+wspZ0Hk6WHyIi5D0dbDmu0jlifsCPZm?=
 =?us-ascii?Q?tIh2droNjXwyCmOQTBp1VREXQu0uHaz3BcFZXGASvXEj3UGhTWKqaQ0c6NYu?=
 =?us-ascii?Q?cgtUOS07oFymlhoN4HlBsTaoUokb2KfaufgWzVEaclB+6GPqr9QUFClTBtJG?=
 =?us-ascii?Q?1UgfoVnNlOVjAOD5BGyAgtsxzlvVYo6ECFiT1AGYmUsUITg+yaXM/F9SiuKv?=
 =?us-ascii?Q?sx7NAUpVY0SW+uJIMlzN2f/IOnHasWE1nkdPQynLJuo1d1tErsKbLZMoMrGS?=
 =?us-ascii?Q?ok+sZ+kD0LQNEENOgLf88sXSPPTpgZLi32JP1xXIkn+pjLOlN6+Nnf3WBuLi?=
 =?us-ascii?Q?lf1gtV1wr7m0Xw8/TnQHPv9zNTZfba5X4n6IrD8RzBjTJ9SIzrKf626JdLAe?=
 =?us-ascii?Q?EuNFRuuYdl+CQtd7RIHFr9prWEuqMnpknDAp03BC/okxFnZyUPRfxbHk+qVl?=
 =?us-ascii?Q?fgfW/4BxjuPUWt2x9PwSDiz4VHKscQ1Jpj3JnzAjIrmUWEp/D9glVL5TCKMw?=
 =?us-ascii?Q?t8PWbtVdOScxGrEfwN3FuV2k0hgXSPXEL3NVSaV2XzwY8MrKGhL4sINSbzha?=
 =?us-ascii?Q?SP+ljCdAAjWLOJtB0AUtOh3IBYa2//Z3FwmKyjDHoJl3t14a7yMmGzoL6BBW?=
 =?us-ascii?Q?nWVeZ4Z1Vlp05Glu5ZESLetmCO4Ln+xfZc9sibS4CI36Wog7s/OXoaCReBef?=
 =?us-ascii?Q?P63ExrE9WFtrT+mMt6iQxek285KlRf3d8+jSIc6IZMWwMyWAf7ZGrJ2LI4V9?=
 =?us-ascii?Q?/tOraDkM4SAOPnfuuVUCcDj4vY+74JuCM/ayBtL3JQmDQuFt0aqcNYY0HuIa?=
 =?us-ascii?Q?Ynu+fK9niKtBHFgFQh/7XGDlbmnabAMJI1Npvy70O07BTz7GAUYEsrjH0cb8?=
 =?us-ascii?Q?lbWFEtlesExN8Tyj8LtylVlePBld0DTxbyWpM6JP/SiwugGFWOwq1013jPbY?=
 =?us-ascii?Q?+U1p6AbEzJOwvedR4cOOeit+HATlFuwzDuVG3eXfQoAvzd70YhDGcgzWKJfq?=
 =?us-ascii?Q?9Xlp/R/faYqN8G7gRNxO9oEudlhPM3r2YvSwTY0cYDWaOhTpwVldXst97TZV?=
 =?us-ascii?Q?HDjv53Hw9EUkPyfb0ZKFQ/FTRBOq0YDuJgTBzdp5kFDsUoBl5mJwY/+/Se9a?=
 =?us-ascii?Q?q4cwTC5J0k8ksJliO0GtQFG8S3tXrF82ufy/8kg9fShbJr29PmkgjgYgRx8o?=
 =?us-ascii?Q?Tu8KK6sham2HvDFD0PiZ+Ds+/6SRp5JnPU4k9KJ/M7n5ysXmbZM82m16YDkH?=
 =?us-ascii?Q?sg=3D=3D?=
X-OriginatorOrg: Nvidia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 85a56818-36f5-452d-e7ee-08dc26bf80b1
X-MS-Exchange-CrossTenant-AuthSource: BYAPR12MB2743.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Feb 2024 02:58:32.1000
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 43083d15-7273-40c1-b7db-39efd9ccc17a
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: ZYYYDo+tDuEOJlM/qLR8bu/ksrUkBB7ad9VnAj0MFxobCXU+ulWiHGSRsB7jc2UVaXzpBHHbJjFotqFEN5gkFg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA1PR12MB8556

On Tue, 06 Feb, 2024 02:49:56 +0000 Joe Damato <jdamato@fastly.com> wrote:
> Make mlx5 compatible with the newly added netlink queue GET APIs.
>
> v1 -> v2:
>   - Move netlink NULL code to mlx5e_deactivate_channel
>   - Move netif_napi_set_irq to mlx5e_open_channel and avoid storing the
>     irq, after netif_napi_add which itself sets the IRQ to -1.
>   - Fix white space where IRQ is stored in mlx5e_open_channel
>
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> ---
>  drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> index c8e8f512803e..3e74c7de6050 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
> @@ -2560,6 +2560,7 @@ static int mlx5e_open_channel(struct mlx5e_priv *priv, int ix,
>  	c->lag_port = mlx5e_enumerate_lag_port(priv->mdev, ix);
>  
>  	netif_napi_add(netdev, &c->napi, mlx5e_napi_poll);
> +	netif_napi_set_irq(&c->napi, irq);
>  
>  	err = mlx5e_open_queues(c, params, cparam);
>  	if (unlikely(err))
> @@ -2602,6 +2603,9 @@ static void mlx5e_activate_channel(struct mlx5e_channel *c)
>  		mlx5e_activate_xsk(c);
>  	else
>  		mlx5e_activate_rq(&c->rq);
> +
> +	netif_queue_set_napi(c->netdev, c->ix, NETDEV_QUEUE_TYPE_TX, &c->napi);
> +	netif_queue_set_napi(c->netdev, c->ix, NETDEV_QUEUE_TYPE_RX, &c->napi);
>  }
>  
>  static void mlx5e_deactivate_channel(struct mlx5e_channel *c)
> @@ -2619,6 +2623,9 @@ static void mlx5e_deactivate_channel(struct mlx5e_channel *c)
>  		mlx5e_deactivate_txqsq(&c->sq[tc]);
>  	mlx5e_qos_deactivate_queues(c);
>  
> +	netif_queue_set_napi(c->netdev, c->ix, NETDEV_QUEUE_TYPE_TX, NULL);
> +	netif_queue_set_napi(c->netdev, c->ix, NETDEV_QUEUE_TYPE_RX, NULL);
> +

I think it would be better to clean the associations before actually
deactivating the queues. Your teardown becomes LIFO/flipped order of
what is done in mlx5_activate_channel.

>  	napi_disable(&c->napi);
>  }

In general, the netdev community maintains a rule for not reposting new
versions of patches in 24hr periods to avoid these types of situations.

Lets add the feedback of updating the commit message feedback in the v1
thread into v3.

       https://lore.kernel.org/netdev/20240206025153.GA11388@fastly.com/T/#mcbf987c817c0d06c29364410ba8ab10b144c753d

Lets send out that v3 a day from now if that's alright. This way we can
pick up feedback from others if needed, but I think we are converging
here.

--
Thanks,

Rahul Rameshbabu