Lines Matching refs:not
30 Pause Frame Forwarding does not work properly on igb
34 For igb devices rte_eth_flow_ctrl_set does not work as expected.
55 The application does not have access to information provided by the hardware
59 The ``ol_flags`` field in the ``rte_mbuf`` structure is not correct and should not be used.
70 The rte_malloc library is not fully implemented
74 The ``rte_malloc`` library is not fully implemented.
77 …All debugging features of rte_malloc library described in architecture documentation are not yet i…
99 The application should not call these functions too often in the main loop.
101 but specific to an lcore and is a cycle reference, not a time reference.
110 HPET timers do not work on the Osage customer reference platform
114 …HPET timers do not work on the Osage customer reference platform which includes an Intel® Xeon® pr…
118 …On Osage boards, the implementation of the ``rte_delay_us()`` function must be changed to not use …
178 …Occasionally, very rarely with 64-bit, this does not occur and a client application will fail on s…
194 Packets are not sent by the 1 GbE/10 GbE SR-IOV driver when the source MAC is not the MAC assigned …
216 SR-IOV drivers do not fully implement the rte_ethdev API
239 Do not use other rte_ethdev API functions in applications that use the SR-IOV drivers.
248 PMD does not work with --no-huge EAL command line parameter
252 …Currently, the DPDK does not store any information about memory allocated by ``malloc()` (for exam…
253 …physical address), hence PMD drivers do not work when the ``--no-huge`` command line parameter is …
256 Sending and receiving data with PMD will not work.
268 Some hardware off-load functions are not supported by the VF Driver
272 Currently, configuration of the following items is not supported by the VF driver:
305 Use newer kernels or do not unbind ports.
314 Twinpond and Ironpond NICs do not report link status correctly
318 Twin Pond/Iron Pond NICs do not bring the physical link down when shutting down the port.
376 Intel® QuickAssist Technology sample application does not work on a 32-bit OS on Shumway
380 The Intel® Communications Chipset 89xx Series device does not fully support NUMA on a 32-bit OS.
400 …10 Gigabit Ethernet devices from Intel do not take VLAN tags into account when calculating packet …
444 processor does not support Intel® AVX.
453 Platforms which processor does not support Intel® AVX.
463 …ceived on the assigned queue, such as ARP packets without 802.1q tags or with the user priority not
475 …It is a NIC's issue due to the following: "In fact, ETQF.UP is not functional, and the information…
507 Devices bound to igb_uio with VT-d enabled do not work on Linux kernel 3.15-3.17
519 Devices will not be allowed to access memory, resulting in following kernel errors::
528 This way we do not need to unbind the device to bind it to igb_uio.
537 VM power manager may not work on systems with more than 64 cores
541 …When using VM power manager on a system with more than 64 cores, VM(s) should not use cores 64 or …
544 VM power manager should not be used with VM(s) that are using cores 64 or above.
547 Do not use cores 64 or above.
556 DPDK may not build on some Intel CPUs using clang < 3.7.0
560 …When compiling DPDK with an earlier version than 3.7.0 of clang, CPU flags are not detected on som…
564 DPDK will not build when using a clang version < 3.7.0.
588 An application should not consider the value in ``argv[]`` as unchanged.
597 I40e VF may not receive packets in the promiscuous mode
601 Promiscuous mode is not supported by the DPDK i40e VF driver when using the
605 The i40e VF does not receive packets when the destination MAC address is unknown.
621 The ``uio_pci_generic`` module is not supported by XL710, since the errata of XL710
622 states that the Interrupt Status bit is not implemented. The errata is the item #71
629 …Status bit. Since it is not supported by X710/XL710/XXV710, it return a *failed* value. The statem…
634 Do not bind the ``uio_pci_generic`` module in X710/XL710/XXV710 NICs.
647 The standard TX function of virtio driver does not manage shared
656 not be modified.
665 headers in the packet data are not shared.
674 igb uio legacy mode can not be used in X710/XL710/XXV710
684 INTx interrupt is not supported by X710/XL710/XXV710, it will cause Input/Output error
688 Do not bind ``igb_uio`` with legacy mode in X710/XL710/XXV710 NICs, or do not use kernel
698 igb_uio can not be used when running l3fwd-power
732 testpmd (and other DPDK applications) will not initialize.
747 The Linux kernel uio_hv_generic driver does not completely shutdown and clean up
751 When application using Netvsc PMD is restarted it can not complete initialization
768 Some kernel drivers are not able to handle the link status correctly
775 kernel drivers may not be able to handle the link status correctly after
866 Not all kernel drivers and not all devices support all IOVA modes. EAL will
873 Some devices (hotplugged or otherwise) may not work due to incompatible IOVA
895 set multiple times are not consistent.