Alexandre Courbot:
>
> MyungJoo, the issue of having this feature in the core vs. having it
> as a devfreq "extension" aside, do you agree with the core idea? An
> informl ack for the idea would allow us to start leveraging this for
> the ACTMON driver. With a concrete user it will make it easier
On 5 December 2014 at 14:41, Arto Merilainen wrote:
> (Sorry for the spam. I am resending the series because I noted that
> some of the email addresses were mistyped)
>
> Currently main mechanism to implement scaling using devfreq is
> polling and the device profile is free to set polling interval
On Tue, Dec 9, 2014 at 2:07 AM, Arto Merilainen wrote:
> Hi MyungJoo,
>
> Thank for your answer, see my answers inline.
>
> On 12/08/2014 09:44 AM, MyungJoo Ham wrote:
>>
>> Please let me start with somewhat naive high-level question:
>>What do you mean by watermark in this context?
>
>
> Sorr
Hi MyungJoo,
Thank for your answer, see my answers inline.
On 12/08/2014 09:44 AM, MyungJoo Ham wrote:
Please let me start with somewhat naive high-level question:
What do you mean by watermark in this context?
Sorry for poor choice of naming. "Load threshold interrupt" might be
more appr
On 8 December 2014 at 08:44, MyungJoo Ham wrote:
>> (Sorry for the spam. I am resending the series because I noted that
>> some of the email addresses were mistyped)
>>
>> Currently main mechanism to implement scaling using devfreq is
>> polling and the device profile is free to set polling interv
> (Sorry for the spam. I am resending the series because I noted that
> some of the email addresses were mistyped)
>
> Currently main mechanism to implement scaling using devfreq is
> polling and the device profile is free to set polling interval.
> However, in many cases this approach is not opti
6 matches
Mail list logo
