#. Performance issue isolation
- * The functions running on CPU cores without context switches are the
- performing scenarios. Identify lcore with ``rte_lcore`` and lcore index
- mapping with CPU using ``rte_lcore_index``.
-
* The functions running on CPU cores without context switches are the
performing scenarios. Identify lcore with ``rte_lcore`` and lcore index
mapping with CPU using ``rte_lcore_index``.
#. Configuration issue isolation
- * Identify core role using ``rte_eal_lcore_role`` to identify RTE, OFF and
- SERVICE. Check performance functions are mapped to run on the cores.
+ * Identify core role using ``rte_eal_lcore_role`` to identify RTE, OFF,
+ SERVICE and NON_EAL. Check performance functions are mapped to run on the
+ cores.
* For high-performance execution logic ensure running it on correct NUMA
- and non-master core.
+ and worker core.
- * Analyze run logic with ``rte_dump_stack``, ``rte_dump_registers`` and
+ * Analyze run logic with ``rte_dump_stack`` and
``rte_memdump`` for more insights.
* Make use of objdump to ensure opcode is matching to the desired state.
for drops for hierarchy, schedulers and WRED configurations.
-Is the packet not in the unexpected format?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Is the packet in the unexpected format?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Packet capture before and after processing :numref:`dtg_pdump`.