[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240531181803.GO491852@kernel.org>
Date: Fri, 31 May 2024 19:18:03 +0100
From: Simon Horman <horms@...nel.org>
To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
jacob.e.keller@...el.com, michal.kubiak@...el.com,
maciej.fijalkowski@...el.com, sridhar.samudrala@...el.com,
przemyslaw.kitszel@...el.com, wojciech.drewek@...el.com,
pio.raczynski@...il.com, jiri@...dia.com,
mateusz.polchlopek@...el.com, shayd@...dia.com,
kalesh-anakkur.purayil@...adcom.com
Subject: Re: [iwl-next v3 13/15] ice: support subfunction devlink Tx topology
On Tue, May 28, 2024 at 06:38:11AM +0200, Michal Swiatkowski wrote:
> Flow for creating Tx topology is the same as for VF port representors,
> but the devlink port is stored in different place (sf->devlink_port).
>
> When creating VF devlink lock isn't taken, when creating subfunction it
> is. Setting Tx topology function needs to take this lock, check if it
> was taken before to not do it twice.
>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@...el.com>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@...el.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists