From: Darren Hart <dvhltc@us.ibm.com>
To: Antoine Martin <antoine@nagafix.co.uk>,
"lkml, " <linux-kernel@vger.kernel.org>
Subject: Source for
Date: Fri, 26 Feb 2010 11:27:56 -0800 [thread overview]
Message-ID: <4B8820BC.4080300@us.ibm.com> (raw)
I'm doing some research into usage of sched_yield() with the hope of
coming up with some best practices and possibly some improved
alternatives using futexes. I found the following thread on the subject:
CFS: new java yield graphs
http://lkml.org/lkml/2007/9/25/463
It presents a nice set of data collected regarding various sched_yield()
scenarios.
http://devloop.org.uk/lkml/
A link to the source was provided, but has since bitrotted as the URL
brings up a blank page, as does the TLD by itself.
Is there another location now hosting the sources that were here:
http://bugs.devloop.org.uk/devloop/browser/metastores/examples-test/src/com/metastores/examples/perftest/
Perhaps somewhere under this domain?:
http://mts.devloop.org.uk/
Thanks,
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
reply other threads:[~2010-02-26 19:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B8820BC.4080300@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=antoine@nagafix.co.uk \
--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