Changes to Readme.md

README.md

@@ -110,14 +110,15 @@ The simulation used in the thesis was ```dpdkOneNode.cc```
 
 1. To run dpdkOneNode some parameters might need to be changed:
 
-* dpdkDriver: refer to the PCI-address of your NIC to be used in the simulation
-    * You can use this command in the terminal to get more info about the NIC's and their PCI addresses.
+* ```dpdkDriver```: Set which driver to use with DPDK.
+* ```dev[]```: Array of strings that contain the PCI-address(es) of your NIC(s) to be used in the simulation.
+    * You can use the following command in the terminal to get more info about the NIC's and their PCI addresses.
     ```sh
     dpdk-devbind.py -s
     ```
-* lCorelist: Should be the same as you chose to isolate in the GRUB parameter *isolcpus* as it tells the DPDK what cores to use in te simulation
-* firstLCore: Sets the logical core of the first NIC you would like to handle incoming traffic on. Must be part of lCorelist.
-* secLCore: Sets the logical core of the second NIC you would like to handle incoming traffic on. Must be part of lCorelist.
+* ```lCorelist```: Should be the same as you chose to isolate in the GRUB parameter *isolcpus* as it tells the DPDK what cores to use in te simulation
+* ```firstLCore```: Sets the logical core of the first NIC you would like to handle incoming traffic on. Must be part of lCorelist.
+* ```secLCore```: Sets the logical core of the second NIC you would like to handle incoming traffic on. Must be part of lCorelist.
 
 2. The dpdkOneNode accept input parameter
     * ```pcap```: Boolean if you want to write pcap files from the node in the simulation to file