From: Andrew Morton <akpm@linux-foundation.org>
To: mgross@linux.intel.com
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org,
linux-pm@lists.linux-foundation.org, mark.gross@intel.com
Subject: Re: pm qos infrastructure and interface
Date: Wed, 10 Oct 2007 22:17:04 -0700 [thread overview]
Message-ID: <20071010221704.6e438c71.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071004215139.GA20078@linux.intel.com>
On Thu, 4 Oct 2007 14:51:39 -0700 Mark Gross <mgross@linux.intel.com> wrote:
> The following patch is a generalization of the latency.c implementation
> done by Arjan last year. It provides infrastructure for more than one
> parameter, and exposes a user mode interface for processes to register
> pm_qos expectations of processes.
>
>
> This interface provides a kernel and user mode interface for registering
> performance expectations by drivers, subsystems and user space
> applications on one of the parameters.
>
> Currently we have {cpu_dma_latency, network_latency, network_throughput}
> as the initial set of pm_qos parameters.
>
> The infrastructure exposes multiple misc device nodes one per
> implemented parameter. The set of parameters implement is defined by
> pm_qos_power_init() and pm_qos_params.h. This is done because having
> the available parameters being runtime configurable or changeable from a
> driver was seen as too easy to abuse.
I'm a bit surprised that this change appears to have no configurability.
If one has set CONFIG_PM=n (for example), shouldn't it all go away?
next prev parent reply other threads:[~2007-10-11 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 21:51 pm qos infrastructure and interface Mark Gross
2007-10-11 5:17 ` Andrew Morton [this message]
2007-10-11 15:08 ` Mark Gross
2007-10-11 15:38 ` Arjan van de Ven
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=20071010221704.6e438c71.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mark.gross@intel.com \
--cc=mgross@linux.intel.com \
--cc=torvalds@linux-foundation.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