[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <IA3PR11MB89851031CC3D724AB2C0D2E88F1BA@IA3PR11MB8985.namprd11.prod.outlook.com>
Date: Mon, 29 Sep 2025 13:00:21 +0000
From: "Romanowski, Rafal" <rafal.romanowski@...el.com>
To: "mheib@...hat.com" <mheib@...hat.com>, "intel-wired-lan@...ts.osuosl.org"
<intel-wired-lan@...ts.osuosl.org>
CC: "przemyslawx.patynowski@...el.com" <przemyslawx.patynowski@...el.com>,
"jiri@...nulli.us" <jiri@...nulli.us>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "horms@...nel.org" <horms@...nel.org>, "Keller,
Jacob E" <jacob.e.keller@...el.com>, "Loktionov, Aleksandr"
<aleksandr.loktionov@...el.com>, "Nguyen, Anthony L"
<anthony.l.nguyen@...el.com>, "Kitszel, Przemyslaw"
<przemyslaw.kitszel@...el.com>
Subject: RE: [Intel-wired-lan] [PATCH net-next, v4, 2/2] i40e: support generic
devlink param "max_mac_per_vf"
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of
> mheib@...hat.com
> Sent: Sunday, September 7, 2025 12:05 PM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: przemyslawx.patynowski@...el.com; jiri@...nulli.us;
> netdev@...r.kernel.org; horms@...nel.org; Keller, Jacob E
> <jacob.e.keller@...el.com>; Loktionov, Aleksandr
> <aleksandr.loktionov@...el.com>; Nguyen, Anthony L
> <anthony.l.nguyen@...el.com>; Kitszel, Przemyslaw
> <przemyslaw.kitszel@...el.com>; Mohammad Heib <mheib@...hat.com>
> Subject: [Intel-wired-lan] [PATCH net-next, v4, 2/2] i40e: support generic
> devlink param "max_mac_per_vf"
>
> From: Mohammad Heib <mheib@...hat.com>
>
> Currently the i40e driver enforces its own internally calculated per-VF MAC
> filter limit, derived from the number of allocated VFs and available hardware
> resources. This limit is not configurable by the administrator, which makes it
> difficult to control how many MAC addresses each VF may use.
>
> This patch adds support for the new generic devlink runtime parameter
> "max_mac_per_vf" which provides administrators with a way to cap the
> number of MAC addresses a VF can use:
>
> - When the parameter is set to 0 (default), the driver continues to use
> its internally calculated limit.
>
> - When set to a non-zero value, the driver applies this value as a strict
> cap for VFs, overriding the internal calculation.
>
> Important notes:
>
> - The configured value is a theoretical maximum. Hardware limits may
> still prevent additional MAC addresses from being added, even if the
> parameter allows it.
>
> - Since MAC filters are a shared hardware resource across all VFs,
> setting a high value may cause resource contention and starve other
> VFs.
>
> - This change gives administrators predictable and flexible control over
> VF resource allocation, while still respecting hardware limitations.
>
> - Previous discussion about this change:
> https://lore.kernel.org/netdev/20250805134042.2604897-2-
> dhill@...hat.com
> https://lore.kernel.org/netdev/20250823094952.182181-1-
> mheib@...hat.com
>
> Signed-off-by: Mohammad Heib <mheib@...hat.com>
> Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@...el.com>
> Reviewed-by: Simon Horman <horms@...nel.org>
> ---
> Documentation/networking/devlink/i40e.rst | 32 +++++++++++++
> drivers/net/ethernet/intel/i40e/i40e.h | 4 ++
> .../net/ethernet/intel/i40e/i40e_devlink.c | 48 ++++++++++++++++++-
> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 31 ++++++++----
> 4 files changed, 105 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/networking/devlink/i40e.rst
> b/Documentation/networking/devlink/i40e.rst
> index d3cb5bb5197e..7480f0300fdb 100644
> --- a/Documentation/networking/devlink/i40e.rst
> +++ b/Documentation/networking/devlink/i40e.rst
> @@ -7,6 +7,38 @@ i40e devlink support
Tested-by: Rafal Romanowski <rafal.romanowski@...el.com>
Powered by blists - more mailing lists