> -----Original Message-----
> From: Intel-wired-lan <[email protected]> On Behalf Of Michal
> Swiatkowski
> Sent: Thursday, June 6, 2024 1:25 PM
> To: [email protected]
> Cc: [email protected]; Fijalkowski, Maciej <[email protected]>;
> [email protected]; Samudrala, Sridhar <[email protected]>;
> Polchlopek, Mateusz <[email protected]>; [email protected];
> [email protected]; [email protected]; Kubiak, Michal
> <[email protected]>; [email protected]; Kitszel, Przemyslaw
> <[email protected]>; Keller, Jacob E <[email protected]>;
> Drewek, Wojciech <[email protected]>
> Subject: [Intel-wired-lan] [iwl-next v5 01/15] ice: add new VSI type for
> subfunctions
> 
> From: Piotr Raczynski <[email protected]>
> 
> Add required plumbing for new VSI type dedicated to devlink subfunctions.
> Make sure that the vsi is properly configured and destroyed. Also allow 
> loading
> XDP and AF_XDP sockets.
> 
> The first implementation of devlink subfunctions supports only one Tx/Rx queue
> pair per given subfunction.
> 
> Reviewed-by: Simon Horman <[email protected]>
> Reviewed-by: Przemek Kitszel <[email protected]>
> Reviewed-by: Wojciech Drewek <[email protected]>
> Signed-off-by: Piotr Raczynski <[email protected]>
> Signed-off-by: Michal Swiatkowski <[email protected]>
> ---
>  drivers/net/ethernet/intel/ice/ice_base.c    |  5 +++-
>  drivers/net/ethernet/intel/ice/ice_dcb_lib.c |  1 +
>  drivers/net/ethernet/intel/ice/ice_lib.c     | 25 ++++++++++++++++++--
>  drivers/net/ethernet/intel/ice/ice_main.c    |  7 ++++--
>  drivers/net/ethernet/intel/ice/ice_type.h    |  1 +
>  drivers/net/ethernet/intel/ice/ice_xsk.c     |  2 +-
>  6 files changed, 35 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/net/ethernet/intel/ice/ice_base.c
> b/drivers/net/ethernet/intel/ice/ice_base.c
> index 912e92c060f6..70f079f279a4 100644
> --- a/drivers/net/ethernet/intel/ice/ice_base.c
> +++ b/drivers/net/ethernet/intel/ice/ice_base.c
> @@ -330,6 +330,9 @@ ice_setup_tx_ctx(struct ice_tx_ring *ring, struct


Tested-by: Rafal Romanowski <[email protected]>



Reply via email to