[Bug 65501] Blind angle of 1% between up_threshold and down_threshold

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=65501

--- Comment #7 from sworddragon2@xxxxxxx ---
> I don't think it ever had it. I checked 2.6.30 and 3.0.. they don't have it. :)

Very interestingly.


> No, that's not right. We will go to max frequency if load has increased over up_threshold, otherwise freq will be proportional to load.

Thanks, this makes things much clearer (especially if I think on another
report). This will now leave a simple question: Why is
MIN_FREQUENCY_UP_THRESHOLD not 1?

-- 
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux