top: limit task cpu % based on total number of threads
authorJim Warner <james.warner@comcast.net>
Tue, 18 Dec 2012 06:00:00 +0000 (00:00 -0600)
committerCraig Small <csmall@enc.com.au>
Sat, 22 Dec 2012 06:10:11 +0000 (17:10 +1100)
commitced5009f759327011488d3c5d0bd3192ff8da009
tree2c51d73f0f96c0f5317e4eb07573da5fe62a1a7f
parent27c2ef1e6d97f403c48510180286ba56a9909ca6
top: limit task cpu % based on total number of threads

Everyone has either accepted this potential distortion
or patched top to eliminate it. Now, the time has come
to regain some consistency when calculating that %CPU.

We'll now limit such values to: 100.0 * total threads.
And, it took way too long to address this little flaw.

(now that we know a '.' + 2 spaces is squeezed to one)
(everything's perfectly justified, but it's just luck)

Reference(s):
http://www.freelists.org/post/procps/top-regression-reports
http://www.freelists.org/post/procps/top-regression-reports,1

Signed-off-by: Jim Warner <james.warner@comcast.net>
top/top.1
top/top.c