[PATCH 02/11] doc/faq: use corelist instead of coremask

[Keith Wiles <keith.wiles@intel.com>]

Signed-off-by: Keith Wiles <keith.wiles@intel.com>
---
 doc/guides/faq/faq.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/guides/faq/faq.rst b/doc/guides/faq/faq.rst
index 5a324b2..98c1e33 100644
--- a/doc/guides/faq/faq.rst
+++ b/doc/guides/faq/faq.rst
@@ -54,7 +54,7 @@ If you need to change the number of pages, it is easier to first remove the page
 See the "Quick Start Setup Script" section in the :ref:`DPDK Getting Started Guide <linux_gsg>` for more information.
 
 
-If I execute "l2fwd -c f -m 64 -n 3 -- -p 3", I get the following output, indicating that there are no socket 0 hugepages to allocate the mbuf and ring structures to?
+If I execute "l2fwd -l 0-3 -m 64 -n 3 -- -p 3", I get the following output, indicating that there are no socket 0 hugepages to allocate the mbuf and ring structures to?
 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
 I have set up a total of 1024 Hugepages (that is, allocated 512 2M pages to each NUMA node).
@@ -80,6 +80,8 @@ For example, if your EAL coremask is 0xff0, the master core will usually be the
 
    taskset 0x10 ./l2fwd -c 0xff0 -n 2
 
+.. Note: Instead of '-c 0xff0' use the '-l 4-11' as a cleaner way to define lcores.
+
 In this way, the hugepages have a greater chance of being allocated to the correct socket.
 Additionally, a ``--socket-mem`` option could be used to ensure the availability of memory for each socket, so that if hugepages were allocated on
 the wrong socket, the application simply will not start.
-- 
2.8.0.GIT