ice: Get switch config, scheduler config and device capabilities
This patch adds to the initialization flow by getting switch
configuration, scheduler configuration and device capabilities.
Switch configuration:
On boot, an L2 switch element is created in the firmware per physical
function. Each physical function is also mapped to a port, to which its
switch element is connected. In other words, this switch can be visualized
as an embedded vSwitch that can connect a physical function's virtual
station interfaces (VSIs) to the egress/ingress port. Egress/ingress
filters will be eventually created and applied on this switch element.
As part of the initialization flow, the driver gets configuration data
from this switch element and stores it.
Scheduler configuration:
The Tx scheduler is a subsystem responsible for setting and enforcing QoS.
As part of the initialization flow, the driver queries and stores the
default scheduler configuration for the given physical function.
Device capabilities:
As part of initialization, the driver has to determine what the device is
capable of (ex. max queues, VSIs, etc). This information is obtained from
the firmware and stored by the driver.
CC: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:08 -07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
|
|
|
/* Copyright (c) 2018, Intel Corporation. */
|
|
|
|
|
|
|
|
#ifndef _ICE_SCHED_H_
|
|
|
|
#define _ICE_SCHED_H_
|
|
|
|
|
|
|
|
#include "ice_common.h"
|
|
|
|
|
2024-04-19 04:08:50 -04:00
|
|
|
/**
|
|
|
|
* DOC: ice_sched.h
|
|
|
|
*
|
|
|
|
* This header file stores everything that is needed for broadly understood
|
|
|
|
* scheduler. It consists of defines related to layers, structures related to
|
|
|
|
* aggregator, functions declarations and others.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define ICE_SCHED_5_LAYERS 5
|
|
|
|
#define ICE_SCHED_9_LAYERS 9
|
|
|
|
|
2022-11-15 11:48:20 +01:00
|
|
|
#define SCHED_NODE_NAME_MAX_LEN 32
|
|
|
|
|
2018-03-20 07:58:13 -07:00
|
|
|
#define ICE_QGRP_LAYER_OFFSET 2
|
2018-03-20 07:58:17 -07:00
|
|
|
#define ICE_VSI_LAYER_OFFSET 4
|
2020-11-20 16:39:27 -08:00
|
|
|
#define ICE_AGG_LAYER_OFFSET 6
|
2019-11-06 02:05:28 -08:00
|
|
|
#define ICE_SCHED_INVAL_LAYER_NUM 0xFF
|
|
|
|
/* Burst size is a 12 bits register that is configured while creating the RL
|
|
|
|
* profile(s). MSB is a granularity bit and tells the granularity type
|
|
|
|
* 0 - LSB bits are in 64 bytes granularity
|
|
|
|
* 1 - LSB bits are in 1K bytes granularity
|
|
|
|
*/
|
|
|
|
#define ICE_64_BYTE_GRANULARITY 0
|
|
|
|
#define ICE_KBYTE_GRANULARITY BIT(11)
|
|
|
|
#define ICE_MIN_BURST_SIZE_ALLOWED 64 /* In Bytes */
|
|
|
|
#define ICE_MAX_BURST_SIZE_ALLOWED \
|
|
|
|
((BIT(11) - 1) * 1024) /* In Bytes */
|
|
|
|
#define ICE_MAX_BURST_SIZE_64_BYTE_GRANULARITY \
|
|
|
|
((BIT(11) - 1) * 64) /* In Bytes */
|
|
|
|
#define ICE_MAX_BURST_SIZE_KBYTE_GRANULARITY ICE_MAX_BURST_SIZE_ALLOWED
|
|
|
|
|
|
|
|
#define ICE_RL_PROF_ACCURACY_BYTES 128
|
|
|
|
#define ICE_RL_PROF_MULTIPLIER 10000
|
|
|
|
#define ICE_RL_PROF_TS_MULTIPLIER 32
|
|
|
|
#define ICE_RL_PROF_FRACTION 512
|
|
|
|
|
2020-11-20 16:39:33 -08:00
|
|
|
#define ICE_PSM_CLK_367MHZ_IN_HZ 367647059
|
|
|
|
#define ICE_PSM_CLK_416MHZ_IN_HZ 416666667
|
|
|
|
#define ICE_PSM_CLK_446MHZ_IN_HZ 446428571
|
|
|
|
#define ICE_PSM_CLK_390MHZ_IN_HZ 390625000
|
|
|
|
|
2019-11-06 02:05:28 -08:00
|
|
|
/* BW rate limit profile parameters list entry along
|
|
|
|
* with bandwidth maintained per layer in port info
|
|
|
|
*/
|
|
|
|
struct ice_aqc_rl_profile_info {
|
|
|
|
struct ice_aqc_rl_profile_elem profile;
|
|
|
|
struct list_head list_entry;
|
|
|
|
u32 bw; /* requested */
|
|
|
|
u16 prof_id_ref; /* profile ID to node association ref count */
|
|
|
|
};
|
2018-03-20 07:58:13 -07:00
|
|
|
|
ice: Get switch config, scheduler config and device capabilities
This patch adds to the initialization flow by getting switch
configuration, scheduler configuration and device capabilities.
Switch configuration:
On boot, an L2 switch element is created in the firmware per physical
function. Each physical function is also mapped to a port, to which its
switch element is connected. In other words, this switch can be visualized
as an embedded vSwitch that can connect a physical function's virtual
station interfaces (VSIs) to the egress/ingress port. Egress/ingress
filters will be eventually created and applied on this switch element.
As part of the initialization flow, the driver gets configuration data
from this switch element and stores it.
Scheduler configuration:
The Tx scheduler is a subsystem responsible for setting and enforcing QoS.
As part of the initialization flow, the driver queries and stores the
default scheduler configuration for the given physical function.
Device capabilities:
As part of initialization, the driver has to determine what the device is
capable of (ex. max queues, VSIs, etc). This information is obtained from
the firmware and stored by the driver.
CC: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:08 -07:00
|
|
|
struct ice_sched_agg_vsi_info {
|
|
|
|
struct list_head list_entry;
|
|
|
|
DECLARE_BITMAP(tc_bitmap, ICE_MAX_TRAFFIC_CLASS);
|
2018-10-26 10:41:02 -07:00
|
|
|
u16 vsi_handle;
|
2020-11-20 16:39:27 -08:00
|
|
|
/* save aggregator VSI TC bitmap */
|
|
|
|
DECLARE_BITMAP(replay_tc_bitmap, ICE_MAX_TRAFFIC_CLASS);
|
ice: Get switch config, scheduler config and device capabilities
This patch adds to the initialization flow by getting switch
configuration, scheduler configuration and device capabilities.
Switch configuration:
On boot, an L2 switch element is created in the firmware per physical
function. Each physical function is also mapped to a port, to which its
switch element is connected. In other words, this switch can be visualized
as an embedded vSwitch that can connect a physical function's virtual
station interfaces (VSIs) to the egress/ingress port. Egress/ingress
filters will be eventually created and applied on this switch element.
As part of the initialization flow, the driver gets configuration data
from this switch element and stores it.
Scheduler configuration:
The Tx scheduler is a subsystem responsible for setting and enforcing QoS.
As part of the initialization flow, the driver queries and stores the
default scheduler configuration for the given physical function.
Device capabilities:
As part of initialization, the driver has to determine what the device is
capable of (ex. max queues, VSIs, etc). This information is obtained from
the firmware and stored by the driver.
CC: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:08 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
struct ice_sched_agg_info {
|
|
|
|
struct list_head agg_vsi_list;
|
|
|
|
struct list_head list_entry;
|
|
|
|
DECLARE_BITMAP(tc_bitmap, ICE_MAX_TRAFFIC_CLASS);
|
|
|
|
u32 agg_id;
|
|
|
|
enum ice_agg_type agg_type;
|
2021-10-15 16:35:15 -07:00
|
|
|
/* bw_t_info saves aggregator BW information */
|
|
|
|
struct ice_bw_type_info bw_t_info[ICE_MAX_TRAFFIC_CLASS];
|
2020-11-20 16:39:27 -08:00
|
|
|
/* save aggregator TC bitmap */
|
|
|
|
DECLARE_BITMAP(replay_tc_bitmap, ICE_MAX_TRAFFIC_CLASS);
|
ice: Get switch config, scheduler config and device capabilities
This patch adds to the initialization flow by getting switch
configuration, scheduler configuration and device capabilities.
Switch configuration:
On boot, an L2 switch element is created in the firmware per physical
function. Each physical function is also mapped to a port, to which its
switch element is connected. In other words, this switch can be visualized
as an embedded vSwitch that can connect a physical function's virtual
station interfaces (VSIs) to the egress/ingress port. Egress/ingress
filters will be eventually created and applied on this switch element.
As part of the initialization flow, the driver gets configuration data
from this switch element and stores it.
Scheduler configuration:
The Tx scheduler is a subsystem responsible for setting and enforcing QoS.
As part of the initialization flow, the driver queries and stores the
default scheduler configuration for the given physical function.
Device capabilities:
As part of initialization, the driver has to determine what the device is
capable of (ex. max queues, VSIs, etc). This information is obtained from
the firmware and stored by the driver.
CC: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:08 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
/* FW AQ command calls */
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2019-02-28 15:24:24 -08:00
|
|
|
ice_aq_query_sched_elems(struct ice_hw *hw, u16 elems_req,
|
2020-06-29 17:27:45 -07:00
|
|
|
struct ice_aqc_txsched_elem_data *buf, u16 buf_size,
|
2019-02-28 15:24:24 -08:00
|
|
|
u16 *elems_ret, struct ice_sq_cd *cd);
|
2022-11-15 11:48:20 +01:00
|
|
|
|
|
|
|
int
|
|
|
|
ice_sched_set_node_bw_lmt(struct ice_port_info *pi, struct ice_sched_node *node,
|
|
|
|
enum ice_rl_type rl_type, u32 bw);
|
|
|
|
|
|
|
|
int
|
|
|
|
ice_sched_set_node_bw(struct ice_port_info *pi, struct ice_sched_node *node,
|
|
|
|
enum ice_rl_type rl_type, u32 bw, u8 layer_num);
|
|
|
|
|
|
|
|
int
|
|
|
|
ice_sched_add_elems(struct ice_port_info *pi, struct ice_sched_node *tc_node,
|
|
|
|
struct ice_sched_node *parent, u8 layer, u16 num_nodes,
|
2022-11-15 11:48:21 +01:00
|
|
|
u16 *num_nodes_added, u32 *first_node_teid,
|
|
|
|
struct ice_sched_node **prealloc_node);
|
2022-11-15 11:48:20 +01:00
|
|
|
|
|
|
|
int
|
|
|
|
ice_sched_move_nodes(struct ice_port_info *pi, struct ice_sched_node *parent,
|
|
|
|
u16 num_items, u32 *list);
|
|
|
|
|
|
|
|
int ice_sched_set_node_priority(struct ice_port_info *pi, struct ice_sched_node *node,
|
|
|
|
u16 priority);
|
|
|
|
int ice_sched_set_node_weight(struct ice_port_info *pi, struct ice_sched_node *node, u16 weight);
|
|
|
|
|
2021-10-07 15:56:57 -07:00
|
|
|
int ice_sched_init_port(struct ice_port_info *pi);
|
|
|
|
int ice_sched_query_res_alloc(struct ice_hw *hw);
|
2020-11-20 16:39:33 -08:00
|
|
|
void ice_sched_get_psm_clk_freq(struct ice_hw *hw);
|
|
|
|
|
2018-10-26 11:44:35 -07:00
|
|
|
void ice_sched_clear_port(struct ice_port_info *pi);
|
ice: Get switch config, scheduler config and device capabilities
This patch adds to the initialization flow by getting switch
configuration, scheduler configuration and device capabilities.
Switch configuration:
On boot, an L2 switch element is created in the firmware per physical
function. Each physical function is also mapped to a port, to which its
switch element is connected. In other words, this switch can be visualized
as an embedded vSwitch that can connect a physical function's virtual
station interfaces (VSIs) to the egress/ingress port. Egress/ingress
filters will be eventually created and applied on this switch element.
As part of the initialization flow, the driver gets configuration data
from this switch element and stores it.
Scheduler configuration:
The Tx scheduler is a subsystem responsible for setting and enforcing QoS.
As part of the initialization flow, the driver queries and stores the
default scheduler configuration for the given physical function.
Device capabilities:
As part of initialization, the driver has to determine what the device is
capable of (ex. max queues, VSIs, etc). This information is obtained from
the firmware and stored by the driver.
CC: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:08 -07:00
|
|
|
void ice_sched_cleanup_all(struct ice_hw *hw);
|
2018-12-19 10:03:28 -08:00
|
|
|
void ice_sched_clear_agg(struct ice_hw *hw);
|
|
|
|
|
2018-03-20 07:58:09 -07:00
|
|
|
struct ice_sched_node *
|
|
|
|
ice_sched_find_node_by_teid(struct ice_sched_node *start_node, u32 teid);
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2018-03-20 07:58:09 -07:00
|
|
|
ice_sched_add_node(struct ice_port_info *pi, u8 layer,
|
2022-11-15 11:48:21 +01:00
|
|
|
struct ice_aqc_txsched_elem_data *info,
|
|
|
|
struct ice_sched_node *prealloc_node);
|
2022-11-15 11:48:20 +01:00
|
|
|
void
|
|
|
|
ice_sched_update_parent(struct ice_sched_node *new_parent,
|
|
|
|
struct ice_sched_node *node);
|
ice: Get switch config, scheduler config and device capabilities
This patch adds to the initialization flow by getting switch
configuration, scheduler configuration and device capabilities.
Switch configuration:
On boot, an L2 switch element is created in the firmware per physical
function. Each physical function is also mapped to a port, to which its
switch element is connected. In other words, this switch can be visualized
as an embedded vSwitch that can connect a physical function's virtual
station interfaces (VSIs) to the egress/ingress port. Egress/ingress
filters will be eventually created and applied on this switch element.
As part of the initialization flow, the driver gets configuration data
from this switch element and stores it.
Scheduler configuration:
The Tx scheduler is a subsystem responsible for setting and enforcing QoS.
As part of the initialization flow, the driver queries and stores the
default scheduler configuration for the given physical function.
Device capabilities:
As part of initialization, the driver has to determine what the device is
capable of (ex. max queues, VSIs, etc). This information is obtained from
the firmware and stored by the driver.
CC: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:08 -07:00
|
|
|
void ice_free_sched_node(struct ice_port_info *pi, struct ice_sched_node *node);
|
|
|
|
struct ice_sched_node *ice_sched_get_tc_node(struct ice_port_info *pi, u8 tc);
|
2018-03-20 07:58:13 -07:00
|
|
|
struct ice_sched_node *
|
2018-09-19 17:23:13 -07:00
|
|
|
ice_sched_get_free_qparent(struct ice_port_info *pi, u16 vsi_handle, u8 tc,
|
2018-03-20 07:58:13 -07:00
|
|
|
u8 owner);
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2018-09-19 17:23:13 -07:00
|
|
|
ice_sched_cfg_vsi(struct ice_port_info *pi, u16 vsi_handle, u8 tc, u16 maxqs,
|
2018-03-20 07:58:17 -07:00
|
|
|
u8 owner, bool enable);
|
2021-10-07 15:56:57 -07:00
|
|
|
int ice_rm_vsi_lan_cfg(struct ice_port_info *pi, u16 vsi_handle);
|
|
|
|
int ice_rm_vsi_rdma_cfg(struct ice_port_info *pi, u16 vsi_handle);
|
2020-11-20 16:39:27 -08:00
|
|
|
|
|
|
|
/* Tx scheduler rate limiter functions */
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2020-11-20 16:39:27 -08:00
|
|
|
ice_cfg_agg(struct ice_port_info *pi, u32 agg_id,
|
|
|
|
enum ice_agg_type agg_type, u8 tc_bitmap);
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2020-11-20 16:39:27 -08:00
|
|
|
ice_move_vsi_to_agg(struct ice_port_info *pi, u32 agg_id, u16 vsi_handle,
|
|
|
|
u8 tc_bitmap);
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2019-11-06 02:05:28 -08:00
|
|
|
ice_cfg_q_bw_lmt(struct ice_port_info *pi, u16 vsi_handle, u8 tc,
|
|
|
|
u16 q_handle, enum ice_rl_type rl_type, u32 bw);
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2019-11-06 02:05:28 -08:00
|
|
|
ice_cfg_q_bw_dflt_lmt(struct ice_port_info *pi, u16 vsi_handle, u8 tc,
|
|
|
|
u16 q_handle, enum ice_rl_type rl_type);
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2021-09-13 11:22:19 -07:00
|
|
|
ice_cfg_vsi_bw_lmt_per_tc(struct ice_port_info *pi, u16 vsi_handle, u8 tc,
|
|
|
|
enum ice_rl_type rl_type, u32 bw);
|
2021-10-07 15:56:57 -07:00
|
|
|
int
|
2021-09-13 11:22:19 -07:00
|
|
|
ice_cfg_vsi_bw_dflt_lmt_per_tc(struct ice_port_info *pi, u16 vsi_handle, u8 tc,
|
|
|
|
enum ice_rl_type rl_type);
|
2021-10-07 15:56:57 -07:00
|
|
|
int ice_cfg_rl_burst_size(struct ice_hw *hw, u32 bytes);
|
2023-06-20 15:18:47 -07:00
|
|
|
int
|
|
|
|
ice_sched_suspend_resume_elems(struct ice_hw *hw, u8 num_nodes, u32 *node_teids,
|
|
|
|
bool suspend);
|
|
|
|
struct ice_sched_node *
|
|
|
|
ice_sched_get_agg_node(struct ice_port_info *pi, struct ice_sched_node *tc_node,
|
|
|
|
u32 agg_id);
|
|
|
|
u8 ice_sched_get_agg_layer(struct ice_hw *hw);
|
|
|
|
u8 ice_sched_get_vsi_layer(struct ice_hw *hw);
|
|
|
|
struct ice_sched_node *
|
|
|
|
ice_sched_get_free_vsi_parent(struct ice_hw *hw, struct ice_sched_node *node,
|
|
|
|
u16 *num_nodes);
|
|
|
|
int
|
|
|
|
ice_sched_add_nodes_to_layer(struct ice_port_info *pi,
|
|
|
|
struct ice_sched_node *tc_node,
|
|
|
|
struct ice_sched_node *parent, u8 layer,
|
|
|
|
u16 num_nodes, u32 *first_node_teid,
|
|
|
|
u16 *num_nodes_added);
|
2020-11-20 16:39:27 -08:00
|
|
|
void ice_sched_replay_agg_vsi_preinit(struct ice_hw *hw);
|
|
|
|
void ice_sched_replay_agg(struct ice_hw *hw);
|
2023-09-12 07:59:33 -04:00
|
|
|
int ice_aq_move_sched_elems(struct ice_hw *hw, struct ice_aqc_move_elem *buf,
|
|
|
|
u16 buf_size, u16 *grps_movd);
|
2021-10-07 15:56:57 -07:00
|
|
|
int ice_replay_vsi_agg(struct ice_hw *hw, u16 vsi_handle);
|
2021-10-07 15:59:03 -07:00
|
|
|
int ice_sched_replay_q_bw(struct ice_port_info *pi, struct ice_q_ctx *q_ctx);
|
ice: Get switch config, scheduler config and device capabilities
This patch adds to the initialization flow by getting switch
configuration, scheduler configuration and device capabilities.
Switch configuration:
On boot, an L2 switch element is created in the firmware per physical
function. Each physical function is also mapped to a port, to which its
switch element is connected. In other words, this switch can be visualized
as an embedded vSwitch that can connect a physical function's virtual
station interfaces (VSIs) to the egress/ingress port. Egress/ingress
filters will be eventually created and applied on this switch element.
As part of the initialization flow, the driver gets configuration data
from this switch element and stores it.
Scheduler configuration:
The Tx scheduler is a subsystem responsible for setting and enforcing QoS.
As part of the initialization flow, the driver queries and stores the
default scheduler configuration for the given physical function.
Device capabilities:
As part of initialization, the driver has to determine what the device is
capable of (ex. max queues, VSIs, etc). This information is obtained from
the firmware and stored by the driver.
CC: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@oracle.com>
Tested-by: Tony Brelinski <tonyx.brelinski@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
2018-03-20 07:58:08 -07:00
|
|
|
#endif /* _ICE_SCHED_H_ */
|