DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Byrne, Stephen1" <stephen1.byrne@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc/proc_info: update support for vdev stats
Date: Mon, 15 Oct 2018 03:36:17 +0000
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2A0459@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <e96c2c2f-8c8e-5751-06e0-e87cf8e69185@intel.com>

Hi Ferruh,

Please find the answers embedded to the email. 

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

The document update is for procinfo tool, which is secondary process to collect stats for NIC interfaces under primary process.
Earlier documentation states since DPDK multi process has limitation in sharing virtual interface stats. The correction updates the same.

but still user may prefer
> to use virtual device as process only.

Proc info info tool purpose is collect stats from primary. Hence whether the primary process uses physical or virtual it is user discretion. But collecting stats is possible for any NIC device via proc info tool.

> Not sure if it worth mentioning stats retrieving supported when virtual device is
> shared between processes, what do you think?

With the above reasoning, I believe proc info tool is state it can collect stats from both virtual and physical NIC is correct.


  reply	other threads:[~2018-10-15  3:36 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
2018-10-15  3:36   ` Varghese, Vipin [this message]
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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2A0459@BGSMSX101.gar.corp.intel.com \
    --to=vipin.varghese@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=stephen1.byrne@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