summary refs log tree commit diff
path: root/arch/arm64/kvm
diff options
context:
space:
mode:
authorJack Morgenstein <jackm@dev.mellanox.co.il>2017-02-23 12:02:44 +0200
committerDavid S. Miller <davem@davemloft.net>2017-02-23 10:57:57 -0500
commit6ed63d845e7866ff1a0eac9f0fa554fdf2c64e1d (patch)
treed699fcce2d85f9e75a045b41f8801b7493ff15d2 /arch/arm64/kvm
parent95f1ba9a24af9769f6e20dfe9a77c863f253f311 (diff)
downloadlinux-6ed63d845e7866ff1a0eac9f0fa554fdf2c64e1d.tar.gz
net/mlx4_core: Use cq quota in SRIOV when creating completion EQs
When creating EQs to handle CQ completion events for the PF
or for VFs, we create enough EQE entries to handle completions
for the max number of CQs that can use that EQ.

When SRIOV is activated, the max number of CQs a VF (or the PF) can
obtain is its CQ quota (determined by the Hypervisor resource tracker).
Therefore, when creating an EQ, the number of EQE entries that the VF
should request for that EQ is the CQ quota value (and not the total
number of CQs available in the FW).

Under SRIOV, the PF, also must use its CQ quota, because
the resource tracker also controls how many CQs the PF can obtain.

Using the FW total CQs instead of the CQ quota when creating EQs resulted
wasting MTT entries, due to allocating more EQEs than were needed.

Fixes: 5a0d0a6161ae ("mlx4: Structures and init/teardown for VF resource quotas")
Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
Reported-by: Dexuan Cui <decui@microsoft.com>
Signed-off-by: Tariq Toukan <tariqt@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch/arm64/kvm')
0 files changed, 0 insertions, 0 deletions