Hi, Doug Smythies wrote: > On my computer, and from a different thread from yesterday, I let > the proposed "wang" patch multiple processes test continue for > another 24 hours. The png file showing the results is attached, also > available at [1]. [...] > http://www.smythies.com/~doug/network/load_average/load_processes_wang.html Thanks. Now that a nice patch seems to be available that takes care of everything :), it seems like a good moment to make sure that the next time there are scheduler changes people can easily see what they need to do. That is, what information would someone new to this code benefit from in order to keep it working well? I am particularly interested in making sure your tests don't get lost. How about something like this? -- >8 -- Subject: sched: add skeleton load-avg documentation For now this is just a link to http://www.smythies.com/~doug/network/load_average/ which has some useful examples of how to test changes. Signed-off-by: Jonathan Nieder <jrnieder@xxxxxxxxx> --- Documentation/scheduler/00-INDEX | 2 ++ Documentation/scheduler/sched-load.txt | 16 ++++++++++++++++ 2 files changed, 18 insertions(+) create mode 100644 Documentation/scheduler/sched-load.txt diff --git a/Documentation/scheduler/00-INDEX b/Documentation/scheduler/00-INDEX index d2651c47ae27..99c75547282d 100644 --- a/Documentation/scheduler/00-INDEX +++ b/Documentation/scheduler/00-INDEX @@ -6,6 +6,8 @@ sched-design-CFS.txt - goals, design and implementation of the Completely Fair Scheduler. sched-domains.txt - information on scheduling domains. +sched-load.txt + - how load-average code works and how to keep it working. sched-nice-design.txt - How and why the scheduler's nice levels are implemented. sched-rt-group.txt diff --git a/Documentation/scheduler/sched-load.txt b/Documentation/scheduler/sched-load.txt new file mode 100644 index 000000000000..16599993d5aa --- /dev/null +++ b/Documentation/scheduler/sched-load.txt @@ -0,0 +1,16 @@ +load averages +============= + +Reported load averages are by necessity an approximation, but with +care we can make sure they approximate reality most of the time. + +Talk about kernel/sched/core.c, including: + +* what is the expected load average? +* workloads to test, automated testing +* known problems, e.g. limitations due to finite-precision math +* interaction with CPU frequency scaling +* relevant links such as + http://www.smythies.com/~doug/network/load_average/ + +(Peter Zijlstra, Doug Smythies, Charles Wang) -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
