All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Ulrich Drepper <drepper@gmail.com>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH 5/5] futex: fix miss ordered wakeups
Date: Thu, 12 Jun 2008 06:30:02 -0700	[thread overview]
Message-ID: <1213277402.16459.25.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.10.0806121022250.3193@apollo.tec.linutronix.de>


On Thu, 2008-06-12 at 10:56 +0200, Thomas Gleixner wrote:
> On Wed, 11 Jun 2008, Daniel Walker wrote:
> > Adds an additional function call to the sched_setscheduler to update the
> > waiter position of a task if it happens to be waiting on a futex. This
> > ensures that the kernel level waiter ordering is correctly maintained
> > based on the changed priority of the task.
> > 
> > I fixed the locking issue noticed by Thomas Gleixner.
> > 
> > This doesn't address userspace at all, only the kernel level wakeups and
> > kernel level ordering.
> > 
> > The additional locking added to the futex_wait function has no visible speed
> > impact, and only effects waiters which actual enter the kernel.
> 
> The additional locking is just broken and you did not even bother to
> test your changes with lockdep.

I ran it with lockdep enabled , I didn't get any warnings..

> Aside of this, these patches still add 100 lines of code to achieve
> nothing - as dicussed when you previously submitted your changes. 
> 
> Please stop wasting everyone's time with that.

It achieves correct ordering of the futex waiters inside the kernel,
that is in fact _something_ ..

Daniel



  reply	other threads:[~2008-06-12 13:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 20:49 [PATCH 1/5] futex: checkpatch cleanup Daniel Walker
2008-06-11 20:49 ` [PATCH 2/5] futex: update prio on requeue Daniel Walker
2008-06-12  5:22   ` Peter Zijlstra
2008-06-11 20:49 ` [PATCH 3/5] mutex debug: add generic blocked_on usage Daniel Walker
2008-06-12  5:25   ` Peter Zijlstra
2008-06-12 13:21     ` Daniel Walker
2008-06-11 20:49 ` [PATCH 4/5] rtmutex: " Daniel Walker
2008-06-11 20:49 ` [PATCH 5/5] futex: fix miss ordered wakeups Daniel Walker
2008-06-12  6:07   ` Peter Zijlstra
2008-06-12 13:22     ` Daniel Walker
2008-06-12 13:57       ` Peter Zijlstra
2008-06-12 14:04         ` Daniel Walker
2008-06-12  8:56   ` Thomas Gleixner
2008-06-12 13:30     ` Daniel Walker [this message]
2008-06-12 13:33       ` Thomas Gleixner
2008-06-12 13:44         ` Daniel Walker
2008-06-12 15:24           ` Thomas Gleixner
2008-06-12 15:56             ` Daniel Walker
2008-06-12 19:55               ` Thomas Gleixner
2008-06-12 22:09                 ` Daniel Walker
2008-06-12 22:43                   ` Thomas Gleixner
2008-06-12 23:06                     ` Daniel Walker
2008-06-12 23:30                       ` Thomas Gleixner

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=1213277402.16459.25.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=arjan@infradead.org \
    --cc=drepper@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.