From: Arjan van de Ven <arjan@linux.intel.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, len.brown@intel.com, mingo@elte.hu,
akpm@osdl.org, jbarnes@virtuousgeek.org, nickpiggin@yahoo.com.au
Subject: Re: [RFC] maximum latency tracking infrastructure (version 2)
Date: Fri, 25 Aug 2006 21:26:37 +0200 [thread overview]
Message-ID: <44EF4EED.2040904@linux.intel.com> (raw)
In-Reply-To: <1156520608.10471.5.camel@c-67-188-28-158.hsd1.ca.comcast.net>
Daniel Walker wrote:
> On Fri, 2006-08-25 at 13:22 +0200, Arjan van de Ven wrote:
>
>> +void set_acceptable_latency(char *identifier, int usecs);
>> +void modify_acceptable_latency(char *identifier, int usecs);
>> +void remove_acceptable_latency(char *identifier);
>> +void synchronize_acceptable_latency(void);
>> +int system_latency_constraint(void);
>> +
>> +int register_latency_notifier(struct notifier_block * nb);
>> +int unregister_latency_notifier(struct notifier_block * nb);
>
>
> The name space here is bugging me a little. Maybe prefix them with
> "pm_latency" so you'd have "pm_latency_set_acceptable()" ,
> "pm_latency_modify_acceptable()" , something like that. Likewise with
> the file names , "include/linux/pm_latency.h"
>
there is no reason why this should JUST be about power management....
next prev parent reply other threads:[~2006-08-25 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 11:22 [RFC] maximum latency tracking infrastructure (version 2) Arjan van de Ven
2006-08-25 13:30 ` Alexey Dobriyan
2006-08-25 13:34 ` Arjan van de Ven
2006-08-25 13:58 ` Ingo Molnar
2006-08-25 13:43 ` Jan Kiszka
2006-08-25 13:48 ` Arjan van de Ven
2006-08-25 14:18 ` Jan Kiszka
2006-08-25 15:15 ` Jesse Barnes
2006-08-25 15:43 ` Daniel Walker
2006-08-25 19:26 ` Arjan van de Ven [this message]
2006-08-25 19:35 ` Daniel Walker
2006-08-25 22:14 ` Andrew Morton
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=44EF4EED.2040904@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=jbarnes@virtuousgeek.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.