DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Vipin Varghese <vipin.varghese@intel.com>,
	marko.kovacevic@intel.com, dev@dpdk.org,
Subject: Re: [dpdk-dev] [PATCH] doc/proc_info: update support for vdev stats
Date: Fri, 12 Oct 2018 15:25:55 +0100
Message-ID: <e96c2c2f-8c8e-5751-06e0-e87cf8e69185@intel.com> (raw)
In-Reply-To: <20181012113503.43597-1-vipin.varghese@intel.com>

On 10/12/2018 12:35 PM, Vipin Varghese wrote:
> 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.

This support is enabled when device shared between primary & secondary. The
capability to share virtual devices added that is correct, but still user may
prefer to use virtual device as process only.
Not sure if it worth mentioning stats retrieving supported when virtual device
is shared between processes, what do you think?

> 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.

  reply	other threads:[~2018-10-12 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 11:35 Vipin Varghese
2018-10-12 14:25 ` Ferruh Yigit [this message]
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:

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

  git send-email \
    --in-reply-to=e96c2c2f-8c8e-5751-06e0-e87cf8e69185@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=marko.kovacevic@intel.com \
    --cc=stephen1.byrne@intel.com \
    --cc=vipin.varghese@intel.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git