FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=stable%2F9 2018-02-01T13:17:42Z 2018-02-01T13:17:42Z Hans Petter Selasky hselasky@FreeBSD.org 2018-02-01T13:17:42Z urn:sha1:955a5bf76ace6cd0421d6ca93dd4332d8e84b96d Properly implement the cond_resched() function macro in the LinuxKPI. Sponsored by: Mellanox Technologies 2017-11-17T15:32:27Z Hans Petter Selasky hselasky@FreeBSD.org 2017-11-17T15:32:27Z urn:sha1:a5a8a091dc44b084a0545099113b21cc85813eb7 Make the dma_alloc_coherent() function in the LinuxKPI NULL safe with regard to the "dev" argument. Submitted by: Krishnamraju Eraparaju @ Chelsio Sponsored by: Chelsio Communications 2017-08-14T13:25:35Z Hans Petter Selasky hselasky@FreeBSD.org 2017-08-14T13:25:35Z urn:sha1:4f00aa42a77d397b4e1a75abf15ec0aa1ad5b0a4 Merge LinuxKPI changes from DragonflyBSD: - Map more Linux compiler related defines to FreeBSD ones. Sponsored by: Mellanox Technologies 2017-08-14T13:15:13Z Hans Petter Selasky hselasky@FreeBSD.org 2017-08-14T13:15:13Z urn:sha1:2259d2586f51e84794ec0b353d66906bbd67ac13 Implement ACCESS_ONCE(), WRITE_ONCE() and READ_ONCE(). Sponsored by: Mellanox Technologies 2017-08-07T13:27:35Z Hans Petter Selasky hselasky@FreeBSD.org 2017-08-07T13:27:35Z urn:sha1:4f2377f3caddadadfddc2ad0a5d88b8529bef5f0 Remove some dead statistics related code and a structure field from the mlx4en driver which is used by its Linux counterpart, but not under FreeBSD. Sponsored by: Mellanox Technologies 2017-08-07T13:17:57Z Hans Petter Selasky hselasky@FreeBSD.org 2017-08-07T13:17:57Z urn:sha1:446ebe996f21e4e235a97cd88b398edaaf45b1b9 Fix broken usage of the mlx4_read_clock() function: - return value has too small width - cycle_t is unsigned and cannot be less than zero Sponsored by: Mellanox Technologies 2017-05-19T12:56:18Z Hans Petter Selasky hselasky@FreeBSD.org 2017-05-19T12:56:18Z urn:sha1:a38a6ce867c4f1e619c44ef09bcbab8eaf7abe1c Flexible and asymmetric allocation of EQs and MSI-X vectors for PF/VFs. Previously, the mlx4 driver queried the firmware in order to get the number of supported EQs. Under SRIOV, since this was done before the driver notified the firmware how many VFs it actually needs, the firmware had to take into account a worst case scenario and always allocated four EQs per VF, where one was used for events while the others were used for completions. Now, when the firmware supports the asymmetric allocation scheme, denoted by exposing num_sys_eqs > 0 (--> MLX4_DEV_CAP_FLAG2_SYS_EQS), we use the QUERY_FUNC command to query the firmware before enabling SRIOV. Thus we can get more EQs and MSI-X vectors per function. Moreover, when running in the new firmware/driver mode, the limitation that the number of EQs should be a power of two is lifted. Obtained from: Linux (dual BSD/GPLv2 licensed) Submitted by: Dexuan Cui @ microsoft . com Differential Revision: https://reviews.freebsd.org/D8867 Sponsored by: Mellanox Technologies 2017-05-19T12:42:33Z Hans Petter Selasky hselasky@FreeBSD.org 2017-05-19T12:42:33Z urn:sha1:a13d6b41829ba9e41df347fd8002fad1a7f1d41d Change mlx4 QP allocation scheme. When using Blue-Flame, BF, the QPN overrides the VLAN, CV, and SV fields in the WQE. Thus, BF may only be used for QPNs with bits 6,7 unset. The current ethernet driver code reserves a TX QP range with 256b alignment. This is wrong because if there are more than 64 TX QPs in use, QPNs >= base + 65 will have bits 6/7 set. This problem is not specific for the Ethernet driver, any entity that tries to reserve more than 64 BF-enabled QPs should fail. Also, using ranges is not necessary here and is wasteful. The new mechanism introduced here will support reservation for "Eth QPs eligible for BF" for all drivers: bare-metal, multi-PF, and VFs (when hypervisors support WC in VMs). The flow we use is: 1. In mlx4_en, allocate Tx QPs one by one instead of a range allocation, and request "BF enabled QPs" if BF is supported for the function 2. In the ALLOC_RES FW command, change param1 to: a. param1[23:0] - number of QPs b. param1[31-24] - flags controlling QPs reservation Bit 31 refers to Eth blueflame supported QPs. Those QPs must have bits 6 and 7 unset in order to be used in Ethernet. Bits 24-30 of the flags are currently reserved. When a function tries to allocate a QP, it states the required attributes for this QP. Those attributes are considered "best-effort". If an attribute, such as Ethernet BF enabled QP, is a must-have attribute, the function has to check that attribute is supported before trying to do the allocation. In a lower layer of the code, mlx4_qp_reserve_range masks out the bits which are unsupported. If SRIOV is used, the PF validates those attributes and masks out unsupported attributes as well. In order to notify VFs which attributes are supported, the VF uses QUERY_FUNC_CAP command. This command's mailbox is filled by the PF, which notifies which QP allocation attributes it supports. Obtained from: Linux (dual BSD/GPLv2 licensed) Submitted by: Dexuan Cui @ microsoft . com Differential Revision: https://reviews.freebsd.org/D8868 Sponsored by: Mellanox Technologies 2016-10-10T11:36:43Z Hans Petter Selasky hselasky@FreeBSD.org 2016-10-10T11:36:43Z urn:sha1:264fbce276d4e488fab3e50c104748e46b2e06b7 The IORESOURCE_XXX defines should resemble a bitmask while SYS_RES_XXX are not bitmasks. Fix return value of pci_resource_flags() to reflect this change. Sponsored by: Mellanox Technologies 2016-04-07T07:45:31Z Hans Petter Selasky hselasky@FreeBSD.org 2016-04-07T07:45:31Z urn:sha1:fc9e99e266a15b5cc5a27c98eb82325ceec91bc3 Fix bugs in currently unused bit searching loop. Sponsored by: Mellanox Technologies