lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <46F17D03.9090801@nortel.com> Date: Wed, 19 Sep 2007 13:48:19 -0600 From: "Chris Friesen" <cfriesen@...tel.com> To: davids@...master.com CC: "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org> Subject: Re: CFS: some bad numbers with Java/database threading [FIXED] David Schwartz wrote: > Nonsense. The task is always ready-to-run. There is no reason its CPU should > be low. This bug report is based on a misunderstanding of what yielding > means. The yielding task has given up the cpu. The other task should get to run for a timeslice (or whatever the equivalent is in CFS) until the yielding task again "becomes head of the thread list". Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/