DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: "Kovacevic, Marko" <marko.kovacevic@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	"Varghese, Vipin" <vipin.varghese@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: add note in proc info for stats retrieval
Date: Fri, 26 Jan 2018 16:37:33 +0000	[thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C90362A4338D@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <20180124164726.23793-1-marko.kovacevic@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marko Kovacevic
> Sent: Wednesday, January 24, 2018 4:47 PM
> To: dev@dpdk.org
> Cc: Mcnamara, John <john.mcnamara@intel.com>; Varghese, Vipin
> <vipin.varghese@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>
> Subject: [dpdk-dev] [PATCH v1] doc: add note in proc info for stats retrieval
> 
> Note added to outline that using
> proc_info for virtual devices is not supported
> 
> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
> ---
>  doc/guides/tools/proc_info.rst | 3 +++
>  1 file changed, 3 insertions(+)
> 
>  **-m**: Print DPDK memory information.
> +
> +.. NOTE::
> +   NOTE: Stats retrieval using ``proc_info`` is not supported for
> +virtual devices like PCAP and TAP
> --
> 2.9.5

Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>

  reply	other threads:[~2018-01-26 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 16:47 Marko Kovacevic
2018-01-26 16:37 ` Jain, Deepak K [this message]
2018-02-01  2:30 ` Thomas Monjalon

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=A09C9DDE180C7E429EC68E2BFB95C90362A4338D@IRSMSX107.ger.corp.intel.com \
    --to=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@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).