From: david@lang.hm
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: sched_yield() options
Date: Mon, 20 Oct 2008 15:34:07 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0810201531010.21749@asgard.lang.hm> (raw)
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
next reply other threads:[~2008-10-20 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 22:34 david [this message]
2008-10-20 22:53 ` Arnaldo Carvalho de Melo
2008-10-20 23:08 ` david
2008-10-20 23:53 ` David M. Lloyd
2008-10-21 0:44 ` david
2008-10-21 0:57 ` David M. Lloyd
2008-10-21 1:04 ` David Schwartz
2008-10-21 13:42 ` Michal Hocko
2008-10-20 23:02 ` Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.0810201531010.21749@asgard.lang.hm \
--to=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®