From dcb6c2b4e8f85d87b2fdfd3aa2bb53d560ce9a1c Mon Sep 17 00:00:00 2001 From: Philip Knirsch Date: Mon, 2 Feb 2009 13:01:22 +0100 Subject: - Fixed the aggressinvess idea. Rather use system/user settings than have yet another separate configurtion --- README.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.txt b/README.txt index ce0532a..40a1d9f 100644 --- a/README.txt +++ b/README.txt @@ -48,9 +48,11 @@ tuned: together are 100 then this will be a balanced and normalized load - Accumulated weights per tune plugin can be > 100 or < 100. Need to decide whether to automatically normalize it or not -- Tuning aggressivness can be specified from 0 to 100. 0 == no PM, 100 means +/* - Tuning aggressivness can be specified from 0 to 100. 0 == no PM, 100 means always fully tune even under full load. Configurable globally for all tuning - plugins and/or individually + plugins and/or individually */ +- Tuning modes should follow the system/user settings for power management of + the currently running GUI (e.g. presentation mode etc) - all fooLoad() methods always return a hash like this: {cat -> {devname -> {subcat = load}}} to support multiple devices per monitor (e.g. disks, network cards) - Optional parameters for fooLoad() calls: category, subcategory and devname -- cgit