DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vipin Varghese <vipin.varghese@intel.com>
To: john.mcnamara@intel.com, marko.kovacevic@intel.com,
	thomas@monjalon.net, ferruh.yigit@intel.com,
	shreyansh.jain@nxp.com, dev@dpdk.org
Cc: sanjay.padubidri@intel.com, amol.patel@intel.com,
	Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH v6 0/2] guide to debug and troubleshoot.
Date: Tue, 19 Feb 2019 21:27:17 +0530	[thread overview]
Message-ID: <20190219155719.89443-1-vipin.varghese@intel.com> (raw)
In-Reply-To: <20190121104144.67365-2-vipin.varghese@intel.com>

The patch series adds a how-to guide for debugging and troubleshooting tips.

Motivation
==========

DPDK proc-info tool is been enhanced to accommodate the debug information for
the port, traffic manager crypto, ring and mempool contents. With these
additional information, it becomes easy to analyze issues and performance
variance.

But applications are designed based on the target platform, workload, poll mode
drivers, and multi-process. This raises variance in debugging and collecting
data. Hence attempt of patch series is identified such symptoms and share step
by step guide to cover the cases.

Not all possible cases could be covered in a single attempt. But with feedback
and support from the community, this can be expanded.

Status
======

Reviews and changes accommodated. ACK received for documentation and SVG files.

Change Log:
==========

V5:
 - correction for word style and grammar - Thomas Monjalon
 - add license for svg files - Vipin Varghese

V4:
 - Correction for word style - Shreyansh Jain

V3:
 - reorder for removing warning in 'make doc-guides-html' - Thomas Monjalon

V2:
 - add offload flag check - Vipin Varghese
 - change tab to space - Marko Kovacevic
 - spelling correction - Marko Kovacevic
 - remove extra characters - Marko Kovacevic
 - add ACK by Marko - Vipn Varghese
 - add ACK from Marko - Vipin Varghese

Vipin Varghese (2):
  doc: add svg for debug and troubleshoot guide
  doc: add guide for debug and troubleshoot

 doc/guides/howto/debug_troubleshoot_guide.rst | 451 ++++++++++++++++++
 doc/guides/howto/img/dtg_consumer_ring.svg    |  24 +
 doc/guides/howto/img/dtg_crypto.svg           |  21 +
 .../howto/img/dtg_distributor_worker.svg      |  36 ++
 doc/guides/howto/img/dtg_mempool.svg          |  27 ++
 doc/guides/howto/img/dtg_pdump.svg            |  33 ++
 doc/guides/howto/img/dtg_producer_ring.svg    |  24 +
 doc/guides/howto/img/dtg_qos_tx.svg           |  29 ++
 doc/guides/howto/img/dtg_rx_rate.svg          |  25 +
 doc/guides/howto/img/dtg_rx_tx_drop.svg       |  33 ++
 doc/guides/howto/img/dtg_sample_app_model.svg | 110 +++++
 doc/guides/howto/img/dtg_service.svg          |  20 +
 doc/guides/howto/index.rst                    |   1 +
 13 files changed, 834 insertions(+)
 create mode 100644 doc/guides/howto/debug_troubleshoot_guide.rst
 create mode 100644 doc/guides/howto/img/dtg_consumer_ring.svg
 create mode 100644 doc/guides/howto/img/dtg_crypto.svg
 create mode 100644 doc/guides/howto/img/dtg_distributor_worker.svg
 create mode 100644 doc/guides/howto/img/dtg_mempool.svg
 create mode 100644 doc/guides/howto/img/dtg_pdump.svg
 create mode 100644 doc/guides/howto/img/dtg_producer_ring.svg
 create mode 100644 doc/guides/howto/img/dtg_qos_tx.svg
 create mode 100644 doc/guides/howto/img/dtg_rx_rate.svg
 create mode 100644 doc/guides/howto/img/dtg_rx_tx_drop.svg
 create mode 100644 doc/guides/howto/img/dtg_sample_app_model.svg
 create mode 100644 doc/guides/howto/img/dtg_service.svg

-- 
2.17.1

  parent reply	other threads:[~2019-02-19 15:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26  7:08 [dpdk-dev] [PATCH v3 1/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2018-11-26  7:08 ` [dpdk-dev] [PATCH v3 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-01-04  6:37   ` Shreyansh Jain
2019-01-04  7:01     ` Varghese, Vipin
2019-01-16 14:54   ` [dpdk-dev] [PATCH v4 0/2] doci/howto: add debug and troubleshoot guide Vipin Varghese
2019-01-16 14:54     ` [dpdk-dev] [PATCH v4 1/2] doc: add svg for " Vipin Varghese
2019-01-16 14:54     ` [dpdk-dev] [PATCH v4 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-01-18 15:28       ` Kovacevic, Marko
2019-01-21  3:38         ` Varghese, Vipin
2019-01-21 10:41       ` [dpdk-dev] [PATCH v5 0/2] doc/howto: add debug and troubleshoot guide Vipin Varghese
2019-01-21 10:41         ` [dpdk-dev] [PATCH v5 1/2] doc: add svg for " Vipin Varghese
2019-01-28  1:08           ` Thomas Monjalon
2019-01-28 14:28             ` Varghese, Vipin
2019-02-19 15:57           ` Vipin Varghese [this message]
2019-02-19 15:57             ` [dpdk-dev] [PATCH v6 " Vipin Varghese
2019-02-19 15:57             ` [dpdk-dev] [PATCH v6 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-02-25 11:34               ` Mcnamara, John
2019-02-25 15:46                 ` Varghese, Vipin
2019-01-21 10:41         ` [dpdk-dev] [PATCH v5 " Vipin Varghese
2019-01-28  1:30           ` Thomas Monjalon
2019-01-28 14:51             ` Varghese, Vipin
2019-01-28 15:59               ` Thomas Monjalon
2019-02-08  9:21                 ` Varghese, Vipin

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=20190219155719.89443-1-vipin.varghese@intel.com \
    --to=vipin.varghese@intel.com \
    --cc=amol.patel@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=sanjay.padubidri@intel.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=thomas@monjalon.net \
    /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).