From: Darren Hart <dvhltc@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Eric Dumazet <eric.dumazet@gmail.com>,
"Peter W. Morreale" <pmorreale@novell.com>,
Rik van Riel <riel@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Gregory Haskins <ghaskins@novell.com>,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
Chris Mason <chris.mason@oracle.com>,
John Cooper <john.cooper@third-harmonic.com>,
Chris Wright <chrisw@sous-sol.org>,
Ulrich Drepper <drepper@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Avi Kivity <avi@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 4/4] futex: Add FUTEX_LOCK with optional adaptive spinning
Date: Fri, 07 May 2010 09:52:33 -0700 [thread overview]
Message-ID: <4BE44551.2020809@us.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005071818380.3401@localhost.localdomain>
Thomas Gleixner wrote:
> On Wed, 5 May 2010, Darren Hart wrote:
>
>> Add a non-pi TID value based futex locking mechanism. This enables the
>> use of adaptive spinning which was problematic with the basic FUTEX_WAIT
>> operation.
>
> You still do way too much work in that spin code with way too much
> code lines.
>
> Can you try the following (completely uncompiled/untested) patch ?
>
> Thanks,
>
> tglx
> Subject: futex-simplify.patch
> From: Thomas Gleixner <tglx@linutronix.de>
> Date: Fri, 07 May 2010 17:56:38 +0200
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> kernel/futex.c | 42 ++++++++++++------------------------
> kernel/sched.c | 66 ---------------------------------------------------------
> 2 files changed, 14 insertions(+), 94 deletions(-)
>
> + if (to && !to->task) {
> + ret = -ETIMEOUT;
> break;
I had hoped to be able to do it like this too. Unfortunately, we can't
arm the timer until after we set TASK_INTERRUPTIBLE, and we don't do
that until after we give up on spinning.
> -
> - if (timeout) {
> - now = ktime_get();
> - if (timeout->tv64 < now.tv64)
> - break;
> }
This bit clearly needs work. Either via some interpolated time
calculation using something like jiffies, or via another timer that sets
a bit we can check in here.
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
next prev parent reply other threads:[~2010-05-07 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 6:24 [PATCH V6 0/4][RFC] futex: FUTEX_LOCK with optional adaptive spinning Darren Hart
2010-05-06 6:24 ` [PATCH 1/4] futex: replace fshared and clockrt with combined flags Darren Hart
2010-05-06 6:24 ` [PATCH 2/4] futex: add futex_q static initializer Darren Hart
2010-05-06 6:24 ` [PATCH 3/4] futex: refactor futex_lock_pi_atomic Darren Hart
2010-05-06 6:24 ` [PATCH 4/4] futex: Add FUTEX_LOCK with optional adaptive spinning Darren Hart
2010-05-07 16:20 ` Thomas Gleixner
2010-05-07 16:24 ` Peter Zijlstra
2010-05-07 16:30 ` Thomas Gleixner
2010-05-07 16:35 ` Peter Zijlstra
2010-05-07 16:43 ` Thomas Gleixner
2010-05-07 19:05 ` Darren Hart
2010-05-07 16:52 ` Darren Hart [this message]
2010-05-07 19:11 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2010-04-09 5:15 [PATCH V5 0/4][RFC] futex: " dvhltc
2010-04-09 5:15 ` [PATCH 4/4] futex: Add " dvhltc
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=4BE44551.2020809@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=avi@redhat.com \
--cc=chris.mason@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=drepper@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=ghaskins@novell.com \
--cc=john.cooper@third-harmonic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pmorreale@novell.com \
--cc=riel@redhat.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