From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Wodkowski, PawelX" <pawelx.wodkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] examples/ip_pipeline: CPU utilization measurement and display
Date: Tue, 8 Mar 2016 08:05:41 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647968B3B@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <2152992.B2xTvfyGUx@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, March 7, 2016 11:34 AM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Cc: dev@dpdk.org; Wodkowski, PawelX <pawelx.wodkowski@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v2] examples/ip_pipeline: CPU utilization
> measurement and display
>
> 2016-03-07 12:31, Thomas Monjalon:
> > 2016-02-22 14:07, Fan Zhang:
> > > This patch adds CPU utilization measurement and idle cycle rate
> > > computation to packet framework. The measurement is done by
> measuring
> > > the cycles spent while a thread pulls zero packet from RX queue. These
> > > cycles are treated as idle cycles (or headroom). A CLI command is added
> > > to display idle cycle rate of specific thread. The CLI command format is
> > > shown as following:
> > >
> > > t <thread_id> headroom
> > >
> > > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> > > Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> >
> > Applied, thanks
>
> Question: Would you be helped by librte_jobstats?
All we needed for now is retrieving the current TSC value. We might consider using librte_jobstats for the next release.
next prev parent reply other threads:[~2016-03-08 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:07 Fan Zhang
2016-03-07 11:31 ` Thomas Monjalon
2016-03-07 11:33 ` Thomas Monjalon
2016-03-08 8:05 ` Dumitrescu, Cristian [this message]
2016-03-09 6:50 ` Wan, Qun
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=3EB4FA525960D640B5BDFFD6A3D8912647968B3B@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=pawelx.wodkowski@intel.com \
--cc=roy.fan.zhang@intel.com \
--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).