From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: linux-kernel@vger.kernel.org
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-pm@vger.kernel.org, gregkh@linuxfoundation.org,
len.brown@intel.com, arjan@linux.intel.com,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v3 0/6] Power Capping Framework and RAPL Driver
Date: Thu, 17 Oct 2013 00:41:23 +0200 [thread overview]
Message-ID: <2461734.gXdEFC695q@vostro.rjw.lan> (raw)
In-Reply-To: <1381535700-2408-1-git-send-email-srinivas.pandruvada@linux.intel.com>
On Friday, October 11, 2013 04:54:54 PM Srinivas Pandruvada wrote:
> Overview
> With the evolution of technologies, which enables power monitoring and limiting,
> more and more devices are able to constrain their power consumption under certain
> limits. There are several use cases for such technologies:
> - Power monitoring: Each device can report its power consumption.
> - Power Limiting: Setting power limits on the devices allows users to guard against
> platform reaching max system power level.
> - Maximize performance: While staying below a power limit, it allows devices to
> automatically adjust performance to meet demands
> - Dynamic control and re-budgeting: If each device can be constrained to some power,
> extra power can redistributed to other devices, which needs additional performance.
>
> One such example of technologies is RAPL (Running Average Power Limit) mechanism
> available in the latest Intel processors. Intel is slowly adding many devices under
> RAPL control. Also there are other technologies available, for power capping various
> devices. Soon it is very likely that other vendors are also adding or considering
> such implementation.
>
> Power Capping framework is an effort to have a uniform interface available to Linux
> drivers, which will enable
> - A uniform sysfs interface for all devices which can offer power capping
> - A common API for drivers, which will avoid code duplication and easy
> implementation of client drivers.
>
> Also submitting Intel RAPL driver using power capping framework.
Are there any comments or objections against this?
If not, I'd like to queue it up for 3.13.
Thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-10-16 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 23:54 Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 1/6] PowerCap: Documentation Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 2/6] PowerCap: Add class driver Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 3/6] PowerCap: Added to drivers build Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 4/6] x86/msr: add 64bit _on_cpu access functions Srinivas Pandruvada
2013-10-11 23:54 ` [PATCH v3 5/6] bitops: Introduce BIT_ULL Srinivas Pandruvada
2013-10-11 23:55 ` [PATCH v3 6/6] Introduce Intel RAPL power capping driver Srinivas Pandruvada
2013-10-16 22:41 ` Rafael J. Wysocki [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=2461734.gXdEFC695q@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=arjan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=srinivas.pandruvada@linux.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
all inboxes | Powered by JetHome®