DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vipin Varghese <vipin.varghese@intel.com>
To: dev@dpdk.org, marko.kovacevic@intel.com, john.mcnamara@intel.com
Cc: sanjay.padubidri@intel.com, Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH] doc: remove redudant information from guide
Date: Mon,  6 May 2019 09:51:38 +0530	[thread overview]
Message-ID: <20190506042138.29731-1-vipin.varghese@intel.com> (raw)

Remove redudant information from section 'Performance issue isolation'.
Reword for packet capture header.

Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
 doc/guides/howto/debug_troubleshoot.rst | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/doc/guides/howto/debug_troubleshoot.rst b/doc/guides/howto/debug_troubleshoot.rst
index 6abddcd32..cef016b2f 100644
--- a/doc/guides/howto/debug_troubleshoot.rst
+++ b/doc/guides/howto/debug_troubleshoot.rst
@@ -298,10 +298,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``.
@@ -404,8 +400,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`.
 
-- 
2.17.1

             reply	other threads:[~2019-05-06  4:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06  4:21 Vipin Varghese [this message]
2019-05-06  4:21 ` Vipin Varghese
2019-05-06  9:00 ` [dpdk-dev] [PATCH v2] doc: remove redundant information from the guide Vipin Varghese
2019-05-06  9:00   ` Vipin Varghese
2019-05-09 15:21   ` Mcnamara, John
2019-05-09 15:21     ` Mcnamara, John
2019-05-09 22:34     ` Thomas Monjalon
2019-05-09 22:34       ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190506042138.29731-1-vipin.varghese@intel.com \
    --to=vipin.varghese@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=sanjay.padubidri@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).