From: Vipin Varghese <vipin.varghese@intel.com>
To: dev@dpdk.org, marko.kovacevic@intel.com, john.mcnamara@intel.com,
shreyansh.jain@nxp.com
Cc: keith.wiles@intel.com, amit.tamboli@intel.com,
sanjay.padubidri@intel.com, amol.patel@intel.com,
ferruh.yigit@intel.com, Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH v8 0/2] guide to debug and troubleshoot.
Date: Tue, 9 Apr 2019 12:03:42 +0530 [thread overview]
Message-ID: <20190409063344.36564-1-vipin.varghese@intel.com> (raw)
Message-ID: <20190409063342.d8YuXtBULsrwiT7Ma4akU-V55c8ur9z8bHofvKb2VaU@z> (raw)
In-Reply-To: <20190225171222.64134-3-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
==========
V8:
- remove quotes from notes section - John Macnamara
- add quotes for DPDK API and variables - Thomas Monjalon
- update use of JUMBO for rx bottleneck - Vipin Varghese
- Add ACK from v7 - Vipin Varghese
V7:
- add space to note and indent - John Macnamara
V6:
- correction for word style and grammar - Thomas Monjalon
- add license for svg files - Vipin Varghese
v5:
- rework of content - 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 | 464 ++++++++++++++++++
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, 847 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
Future Work
===========
- More use cases.
- Runs as non root.
- Effects of Cache partitioning.
- How to run application as non root user.
--
2.17.1
next prev parent reply other threads:[~2019-04-09 6:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 4:56 [dpdk-dev] [PATCH v1] doc: add meson build to contributing guide Vipin Varghese
2018-10-30 10:54 ` Bruce Richardson
2018-10-30 14:13 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2018-10-30 14:18 ` [dpdk-dev] [PATCH v3] " Vipin Varghese
2018-11-14 14:30 ` Kovacevic, Marko
2018-11-24 18:57 ` Thomas Monjalon
2019-01-10 16:37 ` Varghese, Vipin
2019-01-24 23:05 ` [dpdk-dev] [PATCH v4] doc/patches: " Vipin Varghese
2019-01-28 0:39 ` Thomas Monjalon
2019-01-28 14:27 ` Varghese, Vipin
2019-01-28 14:52 ` Thomas Monjalon
2019-01-28 15:40 ` Varghese, Vipin
2019-01-29 10:10 ` [dpdk-dev] [PATCH v5] " Vipin Varghese
2019-02-12 9:36 ` Thomas Monjalon
2019-02-13 5:38 ` Varghese, Vipin
2019-02-13 5:41 ` [dpdk-dev] [PATCH v6] " Vipin Varghese
2019-02-25 17:12 ` [dpdk-dev] [PATCH v7 0/2] guide to debug and troubleshoot Vipin Varghese
2019-02-25 17:12 ` [dpdk-dev] [PATCH v7 1/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2019-04-01 14:56 ` Mcnamara, John
2019-04-01 14:56 ` Mcnamara, John
2019-02-25 17:12 ` [dpdk-dev] [PATCH v7 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-04-01 14:56 ` Mcnamara, John
2019-04-01 14:56 ` Mcnamara, John
2019-04-05 8:49 ` Thomas Monjalon
2019-04-05 8:49 ` Thomas Monjalon
2019-04-08 3:18 ` Varghese, Vipin
2019-04-08 3:18 ` Varghese, Vipin
2019-04-08 6:45 ` Thomas Monjalon
2019-04-08 6:45 ` Thomas Monjalon
2019-04-09 6:33 ` Varghese, Vipin
2019-04-09 6:33 ` Varghese, Vipin
2019-04-09 6:33 ` Vipin Varghese [this message]
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 0/2] guide to " Vipin Varghese
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 1/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2019-04-09 6:33 ` Vipin Varghese
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-04-09 6:33 ` Vipin Varghese
2019-05-04 22:26 ` [dpdk-dev] [PATCH v8 0/2] guide to " Thomas Monjalon
2019-05-04 22:26 ` Thomas Monjalon
2019-04-01 4:08 ` [dpdk-dev] [PATCH v7 " Varghese, Vipin
2019-04-01 4:08 ` Varghese, Vipin
2019-02-27 11:41 ` [dpdk-dev] [PATCH v6] doc/patches: add meson build to contributing guide Thomas Monjalon
2019-02-27 12:13 ` 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=20190409063344.36564-1-vipin.varghese@intel.com \
--to=vipin.varghese@intel.com \
--cc=amit.tamboli@intel.com \
--cc=amol.patel@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=keith.wiles@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=sanjay.padubidri@intel.com \
--cc=shreyansh.jain@nxp.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).