X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fhowto%2Fdebug_troubleshoot.rst;h=df69fa8bcc24208ae9795eda373d58c4e79f3eac;hb=e8adca1951d45064246b8668946bd12841cfd18b;hp=6abddcd327cca2d40cdb0d6e8a26e2c5a40b01db;hpb=08db7bde16178873851567db7f5f27d49dbd688b;p=dpdk.git

diff --git a/doc/guides/howto/debug_troubleshoot.rst b/doc/guides/howto/debug_troubleshoot.rst
index 6abddcd327..df69fa8bcc 100644
--- a/doc/guides/howto/debug_troubleshoot.rst
+++ b/doc/guides/howto/debug_troubleshoot.rst
@@ -71,8 +71,6 @@ RX Port and associated core :numref:`dtg_rx_rate`.
    * Identify if port Speed and Duplex is matching to desired values with
      ``rte_eth_link_get``.
 
-   * Check ``DEV_RX_OFFLOAD_JUMBO_FRAME`` is set with ``rte_eth_dev_info_get``.
-
    * Check promiscuous mode if the drops do not occur for unique MAC address
      with ``rte_eth_promiscuous_get``.
 
@@ -298,10 +296,6 @@ Custom worker function :numref:`dtg_distributor_worker`.
 
 #. 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``.
@@ -311,13 +305,14 @@ Custom worker function :numref:`dtg_distributor_worker`.
 
 #. 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.
@@ -404,8 +399,8 @@ Traffic Manager on TX interface :numref:`dtg_qos_tx`.
    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`.