Merge pull request #108861 from victorcheng7/patch-2

Patch 2

Author: PRMerger19

articles/virtual-network/setup-dpdk.md

@@ -34,15 +34,15 @@ DPDK can run on Azure virtual machines that are supporting multiple operating sy
 
 ## Supported operating systems
 
-The following distributions from the Azure Gallery are supported:
+The following distributions from the Azure Marketplace are supported:
 
-| Linux OS     | Kernel version               | DPDK-18.11   | DPDK-19.11    |
-|--------------|---------------------------   |--------------|-------------- |
-| Ubuntu 16.04 | 4.15.0-1014-azure+           | Pass         | Pass          |
-| Ubuntu 18.04 | 4.15.0-1014-azure+           | Pass         | Pass          |
-| SUSE15SP1    | 4.12.14-8.27-azure+          | Pass         | Pass          |
-| RHEL 7.5     | 3.10.0-862.11.6.el7.x86_64+  | Pass         | Pass          |
-| CentOS 7.5   | 3.10.0-862.11.6.el7.x86_64+  | Pass         | Pass          |
+| Linux OS     | Kernel version               | 
+|--------------|---------------------------   |
+| Ubuntu 16.04 | 4.15.0-1014-azure+           | 
+| Ubuntu 18.04 | 4.15.0-1014-azure+           |
+| SLES 15 SP1  | 4.12.14-8.27-azure+          | 
+| RHEL 7.5     | 3.10.0-862.11.6.el7.x86_64+  | 
+| CentOS 7.5   | 3.10.0-862.11.6.el7.x86_64+  | 
 
 **Custom kernel support**
 
@@ -82,7 +82,7 @@ sudo dracut --add-drivers "mlx4_en mlx4_ib mlx5_ib" -f
 yum install -y gcc kernel-devel-`uname -r` numactl-devel.x86_64 librdmacm-devel libmnl-devel
 ```
 
-### SLES 15
+### SLES 15 SP1
 
 **Azure kernel**
 
@@ -104,7 +104,7 @@ zypper \
 
 ## Set up the virtual machine environment (once)
 
-1. [Download the latest DPDK](https://core.dpdk.org/download). Version 18.02 or higher is required for Azure.
+1. [Download the latest DPDK](https://core.dpdk.org/download). Version 18.11 LTS or 19.11 LTS is required for Azure.
 2. Build the default config with `make config T=x86_64-native-linuxapp-gcc`.
 3. Enable Mellanox PMDs in the generated config with `sed -ri 's,(MLX._PMD=)n,\1y,' build/.config`.
 4. Compile with `make`.
@@ -116,7 +116,7 @@ After restarting, run the following commands once:
 
 1. Hugepages
 
-   * Configure hugepage by running the following command, once for all numanodes:
+   * Configure hugepage by running the following command, once for each numa node:
 
      ```bash
      echo 1024 | sudo tee /sys/devices/system/node/node*/hugepages/hugepages-2048kB/nr_hugepages
@@ -126,21 +126,21 @@ After restarting, run the following commands once:
    * Mount hugepages with `mount -t hugetlbfs nodev /mnt/huge`.
    * Check that hugepages are reserved with `grep Huge /proc/meminfo`.
 
-     > [!NOTE]
+     > [NOTE]
      > There is a way to modify the grub file so that hugepages are reserved on boot by following the [instructions](https://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#use-of-hugepages-in-the-linux-environment) for the DPDK. The instructions are at the bottom of the page. When you're using an Azure Linux virtual machine, modify files under **/etc/config/grub.d** instead, to reserve hugepages across reboots.
 
-2. MAC & IP addresses: Use `ifconfig –a` to view the MAC and IP address of the network interfaces. The *VF* network interface and *NETVSC* network interface have the same MAC address, but only the *NETVSC* network interface has an IP address. VF interfaces are running as subordinate interfaces of NETVSC interfaces.
+2. MAC & IP addresses: Use `ifconfig –a` to view the MAC and IP address of the network interfaces. The *VF* network interface and *NETVSC* network interface have the same MAC address, but only the *NETVSC* network interface has an IP address. *VF* interfaces are running as subordinate interfaces of *NETVSC* interfaces.
 
 3. PCI addresses
 
    * Use `ethtool -i <vf interface name>` to find out which PCI address to use for *VF*.
-   * If *eth0* has accelerated networking enabled, make sure that testpmd doesn’t accidentally take over the VF pci device for *eth0*. If the DPDK application accidentally takes over the management network interface and causes you to lose your SSH connection, use the serial console to stop the DPDK application. You can also use the serial console to stop or start the virtual machine.
+   * If *eth0* has accelerated networking enabled, make sure that testpmd doesn’t accidentally take over the *VF* pci device for *eth0*. If the DPDK application accidentally takes over the management network interface and causes you to lose your SSH connection, use the serial console to stop the DPDK application. You can also use the serial console to stop or start the virtual machine.
 
 4. Load *ibuverbs* on each reboot with `modprobe -a ib_uverbs`. For SLES 15 only, also load *mlx4_ib* with `modprobe -a mlx4_ib`.
 
 ## Failsafe PMD
 
-DPDK applications must run over the failsafe PMD that is exposed in Azure. If the application runs directly over the VF PMD, it doesn't receive **all** packets that are destined to the VM, since some packets show up over the synthetic interface. 
+DPDK applications must run over the failsafe PMD that is exposed in Azure. If the application runs directly over the *VF* PMD, it doesn't receive **all** packets that are destined to the VM, since some packets show up over the synthetic interface. 
 
 If you run a DPDK application over the failsafe PMD, it guarantees that the application receives all packets that are destined to it. It also makes sure that the application keeps running in DPDK mode, even if the VF is revoked when the host is being serviced. For more information about failsafe PMD, see [Fail-safe poll mode driver library](https://doc.dpdk.org/guides/nics/fail_safe.html).