Merge lp:~paelzer/serverguide/serverguide-16.04-dpdk-numa into lp:serverguide/trunk

[Christian Ehrhardt ]

Add dpdk numa configuration info for multi socket systems.

A discussion upstream identified a piece of missing information that now gets added via this MP.

[Doug Smythies (dsmythies)]

O.K. thanks very much.

review: Approve

=== modified file 'serverguide/C/network-config.xml'
--- serverguide/C/network-config.xml	2016-05-06 18:56:14 +0000
+++ serverguide/C/network-config.xml	2016-05-30 06:27:49 +0000
@@ -1469,7 +1469,7 @@
 			  Therefore hugepages have to be configured in your system.
 		  </para>
 		  <para>
-			  The dpdk package has a config file and scripts that try to ease hugepage configuration for dpdk in the form of /etc/dpdk/dpdk.conf.
+			  The dpdk package has a config file and scripts that try to ease hugepage configuration for dpdk in the form of <emphasis>/etc/dpdk/dpdk.conf</emphasis>.
 			  If you have more consumers of hugepages than dpdk in your system or very special requirements how your hugepages are going to be set up you likely want to allocate/control them by yourself.
 			  If not this can be a great simplification to get dpdk to run for yourself.
 		  </para>
@@ -1536,7 +1536,15 @@
 			  Please remember that you have to assign devices to DPDK compatible drivers (see above) before restarting.
 		  </para>
 		  <para>
-			  The section ''--vhost-owner libvirt-qemu:kvm --vhost-perm 0664'' will set vhost_user ports up with owner/permissions to be compatible with Ubuntus way of running qemu-kvm/libvirt with reduced privileges for more security.
+			  The section <emphasis>--vhost-owner libvirt-qemu:kvm --vhost-perm 0664</emphasis> will set vhost_user ports up with owner/permissions to be compatible with Ubuntus way of running qemu-kvm/libvirt with reduced privileges for more security.
+		  </para>
+		  <para>
+			  Please note that the section <emphasis>-m 2048</emphasis> is the most basic numa setup for a single socket system.
+			  If you have multiple sockets you might want to define how to split your memory among them, for example <emphasis>-m 1024, 1024</emphasis>.
+			  Please be aware that DPDK will try to work only with local memory to the network cards it works with (for performance reasons).
+			  That said if you have multiple nodes, but all network cards on one, you should consider spreading your cards.
+			  If not at least allocate your memory to the node where the cards reside, for example in a two node all to node #2: <emphasis>-m 0, 2048</emphasis>.
+			  You can use the tool <emphasis>lstopo</emphasis> from the package <emphasis>hwloc-nox</emphasis> to see on which socket your cards are located.
 		  </para>
 		  <para>
 			  The OpenVswitch you now started supports all port types OpenVswitch usually does, plus DPDK port types.