summaryrefslogtreecommitdiffstats
path: root/sbin/dhclient/dhclient.c
diff options
context:
space:
mode:
authorhselasky <hselasky@FreeBSD.org>2017-05-22 08:17:07 +0000
committerhselasky <hselasky@FreeBSD.org>2017-05-22 08:17:07 +0000
commit23dcad981553a6eed093a676a47643e37b8de63b (patch)
tree1bdba2287f0848d65a47f9e2e4418a8eeb87de45 /sbin/dhclient/dhclient.c
parent58fe5c27ce914e207efbbcefb351003ee5575bdc (diff)
downloadFreeBSD-src-23dcad981553a6eed093a676a47643e37b8de63b.zip
FreeBSD-src-23dcad981553a6eed093a676a47643e37b8de63b.tar.gz
MFC r318531:
mlx4: Use the CQ quota for 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 firmware). 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 firmware total CQs instead of the CQ quota when creating EQs resulted wasting MTT entries, due to allocating more EQEs than were needed. Sponsored by: Mellanox Technologies
Diffstat (limited to 'sbin/dhclient/dhclient.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud