doc: refactor figure numbers into references

[dpdk.git] / doc / guides / nics / vmxnet3.rst

diff --git a/doc/guides/nics/vmxnet3.rst b/doc/guides/nics/vmxnet3.rst
index 3aa5b40..e919088 100644 (file)
--- a/doc/guides/nics/vmxnet3.rst
+++ b/doc/guides/nics/vmxnet3.rst
@@ -121,7 +121,11 @@ The following prerequisites apply:
 *   Before starting a VM, a VMXNET3 interface to a VM through VMware vSphere Client must be assigned.
     This is shown in the figure below.
 
-.. image:: img/vmxnet3_int.*
+.. _figure_vmxnet3_int:
+
+.. figure:: img/vmxnet3_int.*
+
+   Assigning a VMXNET3 interface to a VM using VMware vSphere Client
 
 .. note::
 
@@ -142,31 +146,52 @@ VMXNET3 with a Native NIC Connected to a vSwitch
 
 This section describes an example setup for Phy-vSwitch-VM-Phy communication.
 
-.. image:: img/vswitch_vm.*
+.. _figure_vswitch_vm:
+
+.. figure:: img/vswitch_vm.*
+
+   VMXNET3 with a Native NIC Connected to a vSwitch
 
 .. note::
 
     Other instructions on preparing to use DPDK such as, hugepage enabling, uio port binding are not listed here.
     Please refer to *DPDK Getting Started Guide and DPDK Sample Application's User Guide* for detailed instructions.
 
-The packet reception and transmission flow path is:
+The packet reception and transmission flow path is::
 
-    Packet generator -> 82576 -> VMware ESXi vSwitch -> VMXNET3 device -> Guest VM VMXNET3 port 0 rx burst -> Guest
-    VM 82599 VF port 0 tx burst -> 82599 VF -> Packet generator
+    Packet generator -> 82576
+                     -> VMware ESXi vSwitch
+                     -> VMXNET3 device
+                     -> Guest VM VMXNET3 port 0 rx burst
+                     -> Guest VM 82599 VF port 0 tx burst
+                     -> 82599 VF
+                     -> Packet generator
 
 VMXNET3 Chaining VMs Connected to a vSwitch
 -------------------------------------------
 
 The following figure shows an example VM-to-VM communication over a Phy-VM-vSwitch-VM-Phy communication channel.
 
-.. image:: img/vm_vm_comms.*
+.. _figure_vm_vm_comms:
+
+.. figure:: img/vm_vm_comms.*
+
+   VMXNET3 Chaining VMs Connected to a vSwitch
 
 .. note::
 
     When using the L2 Forwarding or L3 Forwarding applications,
     a destination MAC address needs to be written in packets to hit the other VM's VMXNET3 interface.
 
-In this example, the packet flow path is:
-
-    Packet generator -> 82599 VF -> Guest VM 82599 port 0 rx burst -> Guest VM VMXNET3 port 1 tx burst -> VMXNET3
-    device -> VMware ESXi vSwitch -> VMXNET3 device -> Guest VM VMXNET3 port 0 rx burst -> Guest VM 82599 VF port 1 tx burst -> 82599 VF -> Packet generator
+In this example, the packet flow path is::
+
+    Packet generator -> 82599 VF
+                     -> Guest VM 82599 port 0 rx burst
+                     -> Guest VM VMXNET3 port 1 tx burst
+                     -> VMXNET3 device
+                     -> VMware ESXi vSwitch
+                     -> VMXNET3 device
+                     -> Guest VM VMXNET3 port 0 rx burst
+                     -> Guest VM 82599 VF port 1 tx burst
+                     -> 82599 VF
+                     -> Packet generator