| 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: <alpine.DEB.1.10.0810201531010.21749@asgard.lang.hm> Date: Mon, 20 Oct 2008 15:34:07 -0700 (PDT) From: david@...g.hm To: linux-kernel <linux-kernel@...r.kernel.org> Subject: sched_yield() options I've seen a lot of discussion about how sched_yield is abused by applications. I'm working with a developer on one application that looks like it's falling into this same trap (mutexes between threads and using sched_yield (or more precisely pthread_yield()) to let other threads get the lock) however I've been having a hard time tracking down the appropriate discussions to forward on to the developer (both for why what he's doing is bad, and for what he should be doing instead) could someone point out appropriate mailing list threads, or other documentation for this? David Lang -- 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/
Powered by blists - more mailing lists