How could uptime command show a cpu time greater than 100%? <p>Running an application with an infinite loop (no sleep, no system calls inside the loop) on a linux system with kernel 2.6.11 and single core processor results in a 98-99% cputime consuming. That's normal. I have another single thread server application normally with an average sleep of 98% and a maximum of 20% of cputime. Once connected with a net client, the sleep average drops to 88% (nothing strange) but the cputime (1 minute average) rises constantly but not immediately over the 100%... I saw also a 160% !!?? The net traffic is quite slow (one small packet every 0.5 seconds). Usually the 15 min average of uptime command shows about 115%.</p> <p>I ran also gprof but I did not find it useful... I have a similar scenario:</p> <pre><code>IDLE SCENARIO %time name 59.09 Run() 25.00 updateInfos() 5.68 updateMcuInfo() 2.27 getLastEvent() .... CONNECTED SCENARIO %time name 38.42 updateInfo() 34.49 Run() 10.57 updateCUinfo() 4.36 updateMcuInfo() 3.90 ... 1.77 ... .... </code></pre> <p>None of the listed functions is directly involved with client communication</p> <p>How can you explain this behaviour? Is it a known bug? Could be the extra time consumed in kernel space after a system call and lead to a calculus like</p> <pre><code>%=100*(apptime+kerneltime)/(total apps time)? </code></pre>