From: Vipin Varghese <vipin.varghese@intel.com>
To: marko.kovacevic@intel.com, dev@dpdk.org, stephen1.byrne@intel.com
Cc: Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH] doc/proc_info: update support for vdev stats
Date: Fri, 12 Oct 2018 17:05:03 +0530 [thread overview]
Message-ID: <20181012113503.43597-1-vipin.varghese@intel.com> (raw)
With the latest release, support for vdev ethernet devices like pcap,
tun and tap are been added. Hence collecting statistics using proc-info
is possible now.
Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
doc/guides/tools/proc_info.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/tools/proc_info.rst b/doc/guides/tools/proc_info.rst
index d5b5ed6a6..f62177dba 100644
--- a/doc/guides/tools/proc_info.rst
+++ b/doc/guides/tools/proc_info.rst
@@ -51,7 +51,7 @@ Limitations
mismatch in PMD library arguments can lead to undefined behaviour and results
affecting primary application too.
-* Stats retrieval using ``dpdk-procinfo`` is not supported for virtual devices like PCAP and TAP.
+* Stats retrieval using ``dpdk-procinfo`` is supported for virtual devices like PCAP, TUN and TAP.
* Since default DPDK EAL arguments for ``dpdk-procinfo`` are ``-c1, -n4 & --proc-type=secondary``,
It is not expected that the user passes any EAL arguments.
--
2.17.1
next reply other threads:[~2018-10-12 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 11:35 Vipin Varghese [this message]
2018-10-12 14:25 ` Ferruh Yigit
2018-10-15 3:36 ` Varghese, Vipin
2018-11-09 22:03 ` Ferruh Yigit
2018-11-14 1:52 ` Thomas Monjalon
2018-11-22 22:55 ` Thomas Monjalon
2018-11-23 4:58 ` 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=20181012113503.43597-1-vipin.varghese@intel.com \
--to=vipin.varghese@intel.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=stephen1.byrne@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).