summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/mellanox/mlx5/core/eswitch.h
diff options
context:
space:
mode:
authorMohamad Haj Yahia2016-08-11 10:21:39 +0200
committerLeon Romanovsky2016-10-30 14:43:12 +0100
commit813f854053c26204e2723c498def4c7870dcc7f4 (patch)
treed7f151a2c0e0ea6a6b5075d966a48a99115856be /drivers/net/ethernet/mellanox/mlx5/core/eswitch.h
parentnet/mlx5: Add ConnectX-5 PCIe 4.0 VF device ID (diff)
downloadkernel-qcow2-linux-813f854053c26204e2723c498def4c7870dcc7f4.tar.gz
kernel-qcow2-linux-813f854053c26204e2723c498def4c7870dcc7f4.tar.xz
kernel-qcow2-linux-813f854053c26204e2723c498def4c7870dcc7f4.zip
net/mlx5: Introduce TSAR manipulation firmware commands
TSAR (stands for Transmit Scheduling ARbiter) is a hardware component that is responsible for selecting the next entity to serve on the transmit path. The arbitration defines the QoS policy between the agents connected to the TSAR. The TSAR is a consist two main features: 1) BW Allocation between agents: The TSAR implements a defecit weighted round robin between the agents. Each agent attached to the TSAR is assigned with a weight and it is awarded transmission tokens according to this weight. 2) Rate limer per agent: Each agent attached to the TSAR is (optionally) assigned with a rate limit. TSAR will not allow scheduling for an agent exceeding its defined rate limit. In this patch we implement the API of manipulating the TSAR. Signed-off-by: Mohamad Haj Yahia <mohamad@mellanox.com> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com> Signed-off-by: Leon Romanovsky <leon@kernel.org>
Diffstat (limited to 'drivers/net/ethernet/mellanox/mlx5/core/eswitch.h')
0 files changed, 0 insertions, 0 deletions