[lkml]   [2007]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: pm qos infrastructure and interface
On Thu, 4 Oct 2007 14:51:39 -0700 Mark Gross <> 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?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-10-11 07:19    [W:0.063 / U:30.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site