From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: "Varghese, Vipin" <vipin.varghese@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Byrne, Stephen1" <stephen1.byrne@intel.com>,
"Glynn, Michael J" <michael.j.glynn@intel.com>,
"Patel, Amol" <amol.patel@intel.com>,
"Tummala, Sivaprasad" <sivaprasad.tummala@intel.com>,
"Varghese, Vipin" <vipin.varghese@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: add guide for debug and troubleshoot
Date: Thu, 8 Nov 2018 14:43:24 +0000 [thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F660204DF3D@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20181107093553.28868-1-vipin.varghese@intel.com>
Two spelling mistakes and tabs used instead of space I made the changes.
Just send the patch up.
Builds fine and pdf looks good.
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
> +
> +Debug & Troubleshoot guide via PMD
> +==================================
> +
> +DPDK applications can be designed to run as single thread simple stage
> +to multiple threads with complex pipeline stages. These application can
> +use poll mode devices which helps in offloading CPU cycles. A few
> +models are
> +
> + * single primary
> + * multiple primary
> + * single primary single secondary
> + * single primary multiple secondary
> +
> +In all the above cases, it is a tedious task to isolate, debug and
> +understand odd behaviour which can occurring random or periodic. The
> +goal of guide is to share and explore a few commonly seen patterns and
> +beahviour. Then isolate and identify the root cause via step by step debug
> at various processing stages.
Beahviour/ behaviour
> + RX send rate compared against Receieved rate
> +
Receieved/ Received
> +
> +
> +~~~~~~~~~~~~~~~~~~~~~~~~
> +
Showing up weird characters. For me anyways
Changed it and sent you the patch.
> +How to develop custom code to debug?
> +------------------------------------
> +
> +- For single process – the debug functionality is to be added in same
> + process
> +- For multiple process – the debug functionality can be added to
> + secondary multi process
> +
> +..
> +
> +These can be achieved by Primary’s Debug functions invoked via
> +
> + #. Timer call-back
> + #. Service function under service core
> + #. USR1 or USR2 signal handler
next prev parent reply other threads:[~2018-11-08 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 9:35 Vipin Varghese
2018-11-07 9:35 ` [dpdk-dev] [PATCH 2/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2018-11-08 14:46 ` Kovacevic, Marko
2018-11-08 14:43 ` Kovacevic, Marko [this message]
2018-11-09 10:06 ` [dpdk-dev] [PATCH v2 1/2] doc: add guide for debug and troubleshoot Vipin Varghese
2018-11-09 10:06 ` [dpdk-dev] [PATCH v2 2/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2018-11-09 15:03 ` [dpdk-dev] [PATCH v2 1/2] doc: add guide for debug and troubleshoot Vipin Varghese
2018-11-09 15:03 ` [dpdk-dev] [PATCH v2 2/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2018-11-25 10:21 ` [dpdk-dev] [PATCH v2 1/2] doc: add guide for debug and troubleshoot Thomas Monjalon
2018-11-26 3:53 ` Varghese, Vipin
2018-11-26 7:38 ` Thomas Monjalon
2018-11-26 8:22 ` Varghese, Vipin
2018-12-28 5:30 ` 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=6DC05C7C5F25994B81B3F2F214251F660204DF3D@IRSMSX104.ger.corp.intel.com \
--to=marko.kovacevic@intel.com \
--cc=amol.patel@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=michael.j.glynn@intel.com \
--cc=sivaprasad.tummala@intel.com \
--cc=stephen1.byrne@intel.com \
--cc=vipin.varghese@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).