[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <740e184b-2a7c-4196-835b-09724dc69c6c@intel.com>
Date: Mon, 19 Aug 2024 12:33:02 +0200
From: Przemek Kitszel <przemyslaw.kitszel@...el.com>
To: Michael Chan <michael.chan@...adcom.com>
CC: <netdev@...r.kernel.org>, <edumazet@...gle.com>, <kuba@...nel.org>,
<pabeni@...hat.com>, <pavan.chebbi@...adcom.com>,
<andrew.gospodarek@...adcom.com>, <horms@...nel.org>, <helgaas@...nel.org>,
Hongguang Gao <hongguang.gao@...adcom.com>, Somnath Kotur
<somnath.kotur@...adcom.com>, <davem@...emloft.net>
Subject: Re: [PATCH net-next v2 9/9] bnxt_en: Support dynamic MSIX
On 8/16/24 23:28, Michael Chan wrote:
> A range of MSIX vectors are allocated at initialization for the number
> needed for RocE and L2. During run-time, if the user increases or
> decreases the number of L2 rings, all the MSIX vectors have to be
> freed and a new range has to be allocated. This is not optimal and
> causes disruptions to RoCE traffic every time there is a change in L2
> MSIX.
>
> If the system supports dynamic MSIX allocations, use dynamic
> allocation to add new L2 MSIX vectors or free unneeded L2 MSIX
> vectors. RoCE traffic is not affected using this scheme.
>
> Reviewed-by: Hongguang Gao <hongguang.gao@...adcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@...adcom.com>
> Reviewed-by: Simon Horman <horms@...nel.org>
> Signed-off-by: Michael Chan <michael.chan@...adcom.com>
> ---
> v2: Fix typo in changelog
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 57 +++++++++++++++++++++--
> 1 file changed, 54 insertions(+), 3 deletions(-)
>
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@...el.com>
Powered by blists - more mailing lists