DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] librte_power w/ intel_pstate cpufreq governor
Date: Thu, 14 Jan 2016 02:03:55 -0500	[thread overview]
Message-ID: <20160114070355.GA14958@mhcomputing.net> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A97A800@SHSMSX104.ccr.corp.intel.com>

On Tue, Jan 12, 2016 at 03:17:21PM +0000, Zhang, Helin wrote:
> Hi Matthew
> 
> Yes, you have indicated out the key, the power management module has changed or upgraded.
> Could you help to try the legacy one to see if it still works, as indicated in your link?

I can do this, but according to the documents I am reading, the old Power 
Management module is secretly stubbed out / no-opped inside of the Skylake CPU 
core, and the core manages its own clockrate internally every 1 msec instead 
of every 30 msec with input from the OS (Intel Speed Shift technology).

If this is true, then I suspect there is no point to getting it to work again 
with either the old frequency driver or the new driver, because the chip would 
not listen to it. So then it seems like it makes sense to skip the clock 
adjustment callbacks on Skylake and take extra stuff out of the fastpath code.

> Taking control of the governor from kernel to user space, might need one 
> more checks before that. But it is actually not a big issue, as user can 
> switch it back to anything via 'echo'.

I think it's a bit bigger issue, as it leaves the chip in full-power mode 
without really warning anybody, instead of the standard default adaptive mode. 

> Yes, it seems that librte_power is out of date for a while. It is not easy 
> to track all the kernel versions. Now we have good chance to do that, as you 
> have reported issues. Let's have a look on the new power management 
> mechanism and then see if we can do something.

Yes, let me know how I could help. I don't know very much yet. My machine is 
Skylake Core i7-6700k. Unfortunately I think I am in trouble here, because 
there is no whitepaper on the Intel website for Intel Speed Shift technology 
at all.

> Really thanks to your questions!

I am looking forward to getting some answers figured out together.

> Regards,
> Helin

Matthew.

  reply	other threads:[~2016-01-14  7:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2016-01-14  7:11       ` Matthew Hall
2016-01-14  7:15       ` Zhang, Helin
2016-01-14  7:44         ` Matthew Hall
2017-02-27  5:56 Threqn Peng
2017-03-01  9:22 ` Threqn Peng
2018-03-02  7:18 longtb5
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

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=20160114070355.GA14958@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.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).