http://bugzilla.kernel.org/show_bug.cgi?id=12482 ------- Comment #2 from jimsantelmo@xxxxxxxxx 2009-01-19 08:44 ------- I did some searching (boinc ignore_nice) and found there are some people who actually want boinc processes to run the cpu up to top speed, and were having problems with this because apparently gnome in its infinite wisdom normally automatically sets ignore_nice_load (something that in my opinion a GUI has no business doing) and of course keeps this preference in human-unreadable format. I got curious about SCHED_BATCH and switched my boinc processes to it. The system seems as responsive, and setting ignore_nice_load to zero causes cpu to go to max freq if boinc processes are SCHED_BATCH. SCHED_IDLE is the ultimate nice: a strong case can be made for ignoring SCHED_IDLE time in cpufreq_ondemand, given that SCHED_BATCH is clearly more appropriate for bionc-type jobs if maximum niced performance is desired, and possibly even as the default, given that thruput increases of up to 300% are possible according to `man schedtool` (see below). It would be trivial to extend my patch to keep track of SCHED_BATCH time and allow cpufreq_ondemand to treat that as desired, optionally adding variables to sysfs to control this. SCHED_BATCH [ since 2.6.16 in mainline ] SCHED_BATCH was designed for non-interactive, CPU-bound applications. It uses longer timeslices (to better exploit the cache), but can be interrupted anytime by other processes in other classes to guaratee interaction of the system. Processes in this class are selected last but may result in a considerable speed-up (up to 300%). SCHED_IDLEPRIO [ patch needed ] SCHED_IDLEPRIO is similar to SCHED_BATCH, but was explicitely designed to consume only the time the CPU is idle. No interactive boosting is done. If you used SCHED_BATCH in the -ck kernels this is what you want since 2.6.16 -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- 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
