From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: update overview
Date: Thu, 7 Apr 2016 08:17:12 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC0909034426F4@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1650669.jc1rsQozcN@xps13>
Hi Thomas,
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, April 7, 2016 3:38 PM
> To: Lu, Wenzhuo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] doc: update overview
>
> 2016-04-07 01:34, Lu, Wenzhuo:
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > > stats per queue X X
> > >
> > > You have not filled stats per queue. Is it because of an issue with
> > > queue_stats_mapping?
> > I didn't know it means this function. I'll create a patch to update it. Thanks.
>
> Excuse me, I'm confusing you.
> The "stats per queue" features means the function rte_eth_stats_get() fills the
> arrays q_*.
NP. I missed this part, because I assumed it is a specific API like rte_eth_queue_stats_get. Did not notice the stats are included in rte_eth_stats_get.
I've sent another patch for this mistake.
prev parent reply other threads:[~2016-04-07 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 8:18 [dpdk-dev] [PATCH] " Wenzhuo Lu
2016-04-01 21:33 ` Thomas Monjalon
2016-04-05 0:50 ` Lu, Wenzhuo
2016-04-05 2:54 ` [dpdk-dev] [PATCH v2] " Wenzhuo Lu
2016-04-06 8:25 ` Thomas Monjalon
2016-04-06 8:26 ` Thomas Monjalon
2016-04-07 1:34 ` Lu, Wenzhuo
2016-04-07 7:38 ` Thomas Monjalon
2016-04-07 8:17 ` Lu, Wenzhuo [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=6A0DE07E22DDAD4C9103DF62FEBC0909034426F4@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).