From: Chris Wright <chrisw@sous-sol.org>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Roland Dreier <rdreier@cisco.com>,
"lkml, " <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Gregory Haskins <ghaskins@novell.com>,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
Peter Morreale <pmorreale@novell.com>,
Chris Wright <chrisw@sous-sol.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: RFC: Ideal Adaptive Spinning Conditions
Date: Thu, 1 Apr 2010 10:02:30 -0700 [thread overview]
Message-ID: <20100401170230.GW29241@sequoia.sous-sol.org> (raw)
In-Reply-To: <4BB3FF03.7060400@us.ibm.com>
* Darren Hart (dvhltc@us.ibm.com) wrote:
> Roland Dreier wrote:
>> > I'm looking at some adaptive spinning with futexes as a way to help
>> > reduce the dependence on sched_yield() to implement userspace
>> > spinlocks. Chris, I included you in the CC after reading your comments
>> > regarding sched_yield() at kernel summit and I thought you might be
>> > interested.
>>
>> I think you may have the wrong Chris. Chris Wright wasn't at the most
>> recent kernel summit and I do have a vague recollection of Chris Mason
>> mentioning that Oracle developers found that sched_yield() performed
>> better than futexes + kernel scheduling.
>
> Oh bother, Sorry Chris! I even talked to Chris Wright about this already
> in person and he told me I probably was looking for Chris Mason, and I
> still got the last names crossed up!
No worries Darren, I happen to be interested in the topic too ;-)
(from KVM point of view, which has a slightly different take)
next prev parent reply other threads:[~2010-04-01 17:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 23:21 Darren Hart
2010-03-31 23:35 ` Roland Dreier
2010-04-01 2:03 ` Darren Hart
2010-04-01 17:02 ` Chris Wright [this message]
2010-03-31 23:38 ` Steven Rostedt
2010-04-01 0:17 ` Peter W. Morreale
2010-04-01 2:25 ` Darren Hart
2010-04-03 18:00 ` john cooper
2010-04-05 14:06 ` Darren Hart
2010-04-03 17:51 ` john cooper
2010-04-01 2:13 ` Darren Hart
2010-04-01 2:25 ` Steven Rostedt
2010-04-01 5:15 ` Darren Hart
2010-04-01 12:46 ` Gregory Haskins
2010-04-04 1:50 ` Rik van Riel
2010-04-04 15:06 ` Peter W. Morreale
2010-04-05 14:10 ` Darren Hart
2010-04-01 2:10 ` Darren Hart
2010-04-01 14:04 ` Chris Mason
2010-04-01 14:20 ` Avi Kivity
2010-04-01 15:54 ` Darren Hart
2010-04-01 16:10 ` Avi Kivity
2010-04-01 17:10 ` Darren Hart
2010-04-01 17:15 ` Avi Kivity
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=20100401170230.GW29241@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=dvhltc@us.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pmorreale@novell.com \
--cc=rdreier@cisco.com \
--cc=rostedt@goodmis.org \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome