top misinforming with threads in the mix

Hi,

I wrote a process that spawns a thread and then the thread just goes to town using CPU (on purpose) while the main process waits on it.

On linux-2.6.3 and top 3.1.15 top shows that the machine is 0% idle, but it does not show any processes taking any significant CPU time.

However, things show fine on linux-2.6.11 with top 3.2.5

Does anyone know if this was a top deficiency or something the kernel wasn't reporting correctly?

Thanks,
 Davy


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Linux BKCVS kernel history git import..
• Next by Date: RE: [patch] properly stop devices before poweroff
• Previous by thread: Linux BKCVS kernel history git import..
• Next by thread: RE: [patch] properly stop devices before poweroff
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]