anchor.diff:  
   ==== Performance Cycles/Packet ConnectX-4 vs Intel XL710
   
  -For version TRex v2.11, this is the comparison results between XL710 and ConnectX-4 for various scenarios
  -
  -.Stateless MPPS/Core [Perlimeniary]
  +For TRex version v2.11, these are the comparison results between XL710 and ConnectX-4 for various scenarios.
  +
  +.Stateless MPPS/Core [Preliminary]
   image:images/xl710_vs_mlx5_64b.png[title="Stateless 64B"] 
   
  -.Stateless Gb/Core [Perlimeniary]
  +.Stateless Gb/Core [Preliminary]
   image:images/xl710_vs_mlx5_var_size.png[title="Stateless variable size packet"] 
   
   *Comments*::
    
  -1. For Stateless 64B profiles ConnectX-4 cost 50-90% more cycles per packet (it is actually even more because there is the TRex scheduler overhead) - it means that in the worst case scenario you will need x2 CPU for the same total MPPS
  -2. For Stateless/Stateful 256B profiles, ConnectX-4 cost half of the cycles per packets. ConnectX-4 probably can handle in a better way chained mbuf (scatter gather).
  -3. In Average Stateful senario ConnectX-4 will be slightly better.
  -4. MLX5 can reach ~90MPPS while XL710 limited to 35MPPS 
  +1. For Stateless 64B profiles, ConnectX-4 uses 50-90% more CPU cycles per packet (it is actually even more because there is the TRex scheduler overhead) - it means that in worst case scenario, you will need x2 CPU for the same total MPPS.
  +2. For Stateless/Stateful 256B profiles, ConnectX-4 uses half of the CPU cycles per packet. ConnectX-4 probably can handle in a better way chained mbufs (scatter gather).
  +3. In average stateful senario, ConnectX-4 is slightly better.
  +4. MLX5 can reach ~90MPPS while XL710 is limited to 35MPPS. 
   
   
   [NOTE]
   =====================================
  -There is a task to automate the production of this reports
  +There is a task to automate the production of thess reports
   =====================================
   
   ==== Troubleshooting
  
positive.code: 
  ==== Limitations/Issues
  
  * Stateless per stream statistics is done in software (No hardware support like in X710 card).
  * link:https://trex-tgn.cisco.com/youtrack/issue/trex-272[QSFP+ issue]
  
  
  
negative.code: anchor:connectx_support[]
  
  Mellanox ConnectX-4 adapter family supports 100/56/40/25/10 Gb/s Ethernet speeds. 
  Its DPDK support is a bit different from Intel DPDK support, more information can be found link:http://dpdk.org/doc/guides/nics/mlx5.html[here].
  Intel NICs do not require additional kernel drivers (except for igb_uio which is already supported in most distributions). ConnectX-4 works on top of Infiniband API (verbs) and requires special kernel modules/user space libs. 
  This means that it is required to install OFED package to be able to work with this NIC.
  Installing the full OFED package is the simplest way to make it work (trying to install part of the package can work too but didn't work for us).
  The advantage of this model is that you can control it using standard Linux tools (ethtool and ifconfig will work).
  The disadvantage is the OFED dependency.
  
  ==== Installation  
  
  ==== Install Linux 
  
  We tested the following distro with TRex and OFED. Others might work too.
  
  * CentOS 7.2 
  
  Following distro was tested and did *not* work for us.
  
  * Fedora 21 (3.17.4-301.fc21.x86_64)  
  * Ubuntu 14.04.3 LTS (GNU/Linux 3.19.0-25-generic x86_64)  -- crash when RSS was enabled link:https://trex-tgn.cisco.com/youtrack/issue/trex-294[MLX RSS issue]
  
  ==== Install OFED 
  
  Information was taken from  link:http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers[Install OFED]
  
  * Download 3.4-2 OFED tar for your distro  
  
  [IMPORTANT]
  =====================================
  The version must be *MLNX_OFED_LINUX-3.4-2* 
  =====================================
  
  [IMPORTANT]
  