From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"Byrne, Stephen1" <stephen1.byrne@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc/proc_info: update support for vdev stats
Date: Fri, 23 Nov 2018 04:58:25 +0000 [thread overview]
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2C17A5@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <2494049.8bNKbzAJKt@xps>
Hi Thomas,
With DPDK 18.11-rc4 I still see issues at times, Hence more test is required before I can send the change in request.
Thanks
Vipin Varghese
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, November 23, 2018 4:25 AM
> To: Varghese, Vipin <vipin.varghese@intel.com>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>; Byrne, Stephen1 <stephen1.byrne@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] doc/proc_info: update support for vdev stats
>
> 14/11/2018 02:52, Thomas Monjalon:
> > 09/11/2018 23:03, Ferruh Yigit:
> > > 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.
> > > >
> > > > Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> > >
> > > Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > >
> > > Applied to dpdk-next-net/master, thanks.
> >
> > Sorry, I removed it from the pull to mainline.
> > I think it is wrong listing vdevs as supported in "Limitations".
> > Please send a patch for simply removing the line.
>
> No update?
>
>
prev parent reply other threads:[~2018-11-23 4:58 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
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 [this message]
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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2C17A5@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 \
--cc=thomas@monjalon.net \
/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).