**Description**:
The supported network interface cards can come in a number of variants with different device ID's.
- Not all of these variants have been tested with the Intel® DPDK.
+ Not all of these variants have been tested with the DPDK.
The NIC device identifiers used during testing:
A multi-process client application fails to initialize.
**Resolution/Workaround**:
- See the "Multi-process Limitations" section in the Intel® DPDK Programmer's Guide for more information.
+ See the "Multi-process Limitations" section in the DPDK Programmer's Guide for more information.
**Affected Environment/Platform**:
All.
------------------------------------------------------------------------------------
**Description**:
- When compiling Intel® DPDK (and any DPDK app), gcc may generate Intel® AVX instructions, even when the
+ When compiling DPDK (and any DPDK app), gcc may generate Intel® AVX instructions, even when the
processor does not support Intel® AVX.
**Implication**:
**Driver/Module**:
VM power manager application.
+
+
+DPDK may not build on some Intel CPUs using clang < 3.7.0
+---------------------------------------------------------
+
+**Description**:
+ When compiling DPDK with an earlier version than 3.7.0 of clang, CPU flags are not detected on some Intel platforms
+ such as Intel Broadwell/Skylake (and possibly future CPUs), and therefore compilation fails due to missing intrinsics.
+
+**Implication**:
+ DPDK will not build when using a clang version < 3.7.0.
+
+**Resolution/Workaround**:
+ Use clang 3.7.0 or higher, or gcc.
+
+**Affected Environment/Platform**:
+ Platforms with Intel Broadwell/Skylake using an old clang version.
+
+**Driver/Module**:
+ Environment Abstraction Layer (EAL).