From: Lina Iyer <lina.iyer@linaro.org>
To: Kevin Hilman <khilman@linaro.org>
Cc: daniel.lezcano@linaro.org, ulf.hansson@linaro.org,
linux-pm@vger.kernel.org, tglx@linutronix.de, rjw@rjwysocki.net,
Praveen Chidambaram <pchidamb@codeaurora.org>
Subject: Re: [PATCH v2 2/4] QoS: Enhance framework to support per-cpu PM QoS request
Date: Wed, 27 Aug 2014 14:13:00 -0600 [thread overview]
Message-ID: <20140827201300.GA79706@ilina-mac.domain> (raw)
In-Reply-To: <7hd2blerqz.fsf@paris.lan>
On Wed, Aug 27, 2014 at 11:01:40AM -0700, Kevin Hilman wrote:
>Lina Iyer <lina.iyer@linaro.org> writes:
>
>> QoS request can be better optimized if the request can be set only for
>> the required cpus and not all cpus. This helps save power on other
>> cores, while still gauranteeing the quality of service on the desired
>> cores.
>>
>> Add a new enumeration to specify the PM QoS request type. The enums help
>> specify what is the intended target cpu of the request.
>>
>> Enhance the QoS constraints data structures to support target value for
>> each core. Requests specify if the QoS is applicable to all cores
>> (default) or to a selective subset of the cores or to a core(s).
>>
>> Idle and interested drivers can request a PM QoS value for a constraint
>> across all cpus, or a specific cpu or a set of cpus. Separate APIs have
>> been added to request for individual cpu or a cpumask. The default
>> behaviour of PM QoS is maintained i.e, requests that do not specify a
>> type of the request will continue to be effected on all cores.
>>
>> The userspace sysfs interface does not support setting cpumask of a PM
>> QoS request.
>>
>> Signed-off-by: Praveen Chidambaram <pchidamb@codeaurora.org>
>> Signed-off-by: Lina Iyer <lina.iyer@linaro.org>
>
>I'm curious if you looked at using the per-device QoS API for this
>instead of expending the system-wide API. IOW, from a per-device QoS
>POV, a CPU is no different than any other device, and since we already
>have the per-device QoS API, I wondered if that might be a better choice
>to implment this per-CPU feature.
>
If you mean dev-pm-qos, then yes. I explored using that. The dev-pm-qos
is an user of the qos framework and holds an pm-qos object, but not in
any other way influences the final value of the QoS constraint other
than specify a request on behalf of the device. IMHO, What we want is
complementary. When a device specifies a request, we want the request to
be directed at a set of cpus and that is a function of the QoS
framework, hence addressed by these patches to the QoS framework.
>Kevin
>--
>To unsubscribe from this list: send the line "unsubscribe linux-pm" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-27 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 16:01 [PATCH v2 0/4] PM QoS: per-cpu PM QoS support Lina Iyer
2014-08-13 16:01 ` [PATCH v2 1/4] QoS: Modify data structures and function arguments for scalability Lina Iyer
2014-08-18 23:38 ` Kevin Hilman
2014-08-27 17:44 ` Kevin Hilman
2014-08-13 16:01 ` [PATCH v2 2/4] QoS: Enhance framework to support per-cpu PM QoS request Lina Iyer
2014-08-15 12:37 ` Javi Merino
2014-08-15 15:06 ` Lina Iyer
2014-08-18 23:55 ` Kevin Hilman
2014-08-19 0:34 ` Lina Iyer
2014-08-27 18:01 ` Kevin Hilman
2014-08-27 20:13 ` Lina Iyer [this message]
2014-08-13 16:01 ` [PATCH v2 3/4] irq: Allow multiple clients to register for irq affinity notification Lina Iyer
2014-08-19 0:04 ` Kevin Hilman
2014-08-19 0:17 ` Lina Iyer
2014-08-13 16:01 ` [PATCH v2 4/4] QoS: Enable PM QoS requests to apply only on smp_affinity of an IRQ Lina Iyer
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=20140827201300.GA79706@ilina-mac.domain \
--to=lina.iyer@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=khilman@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=pchidamb@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.org \
/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