From: longtb5@viettel.com.vn
To: <dev@dpdk.org>
Cc: <david.hunt@intel.com>, <mhall@mhcomputing.net>,
<helin.zhang@intel.com>, <longtb5@viettel.com.vn>
Subject: [dpdk-dev] librte_power w/ intel_pstate cpufreq governor
Date: Fri, 2 Mar 2018 14:18:56 +0700 (ICT) [thread overview]
Message-ID: <000201d3b1f7$4b622cc0$e2268640$@viettel.com.vn> (raw)
Hi everybody,
I know this thread was from over 2 years ago but I ran into the same problem
with l3fwd-power today.
Any updates on this?
-BL
next reply other threads:[~2018-03-02 7:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 7:18 longtb5 [this message]
2018-03-02 7:20 ` longtb5
2018-03-05 10:16 ` Hunt, David
2018-03-05 10:48 ` longtb5
2018-03-05 11:25 ` Hunt, David
2018-03-05 12:23 ` longtb5
-- strict thread matches above, loose matches on Subject: below --
2017-02-27 5:56 Threqn Peng
2017-03-01 9:22 ` Threqn Peng
2015-12-06 0:08 Matthew Hall
2016-01-03 7:51 ` Matthew Hall
2016-01-12 15:17 ` Zhang, Helin
2016-01-14 7:03 ` Matthew Hall
2016-01-14 7:11 ` Matthew Hall
2016-01-14 7:15 ` Zhang, Helin
2016-01-14 7:44 ` Matthew Hall
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='000201d3b1f7$4b622cc0$e2268640$@viettel.com.vn' \
--to=longtb5@viettel.com.vn \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=mhall@mhcomputing.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).