DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Yaron Illouz <yaroni@radcom.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ixgbevf missed stats
Date: Fri, 11 Mar 2016 00:47:49 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09090343A1BC@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <VI1PR05MB1406B3A27E7EC25FB4D15806A1B40@VI1PR05MB1406.eurprd05.prod.outlook.com>

Hi Yaron,

> -----Original Message-----
> From: Yaron Illouz [mailto:yaroni@radcom.com]
> Sent: Thursday, March 10, 2016 8:53 PM
> To: Lu, Wenzhuo; dev@dpdk.org
> Subject: RE: ixgbevf missed stats
> 
> So I can't know if there where dropps!!!
Missed means the RX buffer is not enough. What's in my mind is that there's only one buffer shared, so we cannot split it to every VF. So, for VF, we have to check the PF stats to know there's jam.

> Is this the same for dpdk with virtio? Can I know if there where dropps?
I think this's another story. Let's wait and see what the virtio experts will teach us :)

> 
> -----Original Message-----
> From: Lu, Wenzhuo [mailto:wenzhuo.lu@intel.com]
> Sent: Thursday, March 10, 2016 2:40 PM
> To: Yaron Illouz <yaroni@radcom.com>; dev@dpdk.org
> Subject: RE: ixgbevf missed stats
> 
> Hi Yaron,
> The stats of PF is done by HW. The bad news is I don' find anything for VF. I also
> doubt if there's corresponding stats for VF.
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yaron Illouz
> > Sent: Thursday, March 10, 2016 8:27 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] ixgbevf missed stats
> >
> > Hi
> >
> > There is no statistics of missed packet for ixgbevf in a vm.
> > How can I get these stats?
> > In ixgbe it is called imissed

  reply	other threads:[~2016-03-11  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 12:27 Yaron Illouz
2016-03-10 12:40 ` Lu, Wenzhuo
2016-03-10 12:53   ` Yaron Illouz
2016-03-11  0:47     ` Lu, Wenzhuo [this message]
2016-03-11  0:52       ` 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=6A0DE07E22DDAD4C9103DF62FEBC09090343A1BC@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=yaroni@radcom.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).