From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: [RFC][PATCH RT 0/2] futex priority based wakeup
Date: Wed, 10 May 2006 11:26:51 +0200 [thread overview]
Message-ID: <20060510112651.24a36e7b@frecb000686> (raw)
Hi,
in the current futex implementation, tasks are woken up in FIFO order,
(i.e. in the order they were put to sleep). For realtime systems needing
system wide strict realtime priority scheduling, tasks should be woken up
in priority order.
This patchset achieves this by changing the futex hash bucket list into
a plist. Tasks waiting on a futex are enqueued in this plist based on
their priority so that they can be woken up in priority order.
The 1st patch is a small optimization to futex_requeue() which could
go into mainline and does not depend on the RT patch.
The 2nd patch does the real job of converting the futex hash bucket list
into a plist.
There is however a drawback with this patch in that it is not possible to use
CONFIG_DEBUG_PI_LIST as the plist debugging code expects the spinlock protecting
the plist to be a raw_spinlock while the futex hash bucket lock is a regular
spinlock (rt-mutex). Maybe the plist debugging checks could be made generic to
accept both types.
Any thoughts?
Comments welcomed.
Sébastien.
-----------------------------------------------------
Sébastien Dugué BULL/FREC:B1-247
phone: (+33) 476 29 77 70 Bullcom: 229-7770
mailto:sebastien.dugue@bull.net
Linux POSIX AIO: http://www.bullopensource.org/posix
http://sourceforge.net/projects/paiol
-----------------------------------------------------
next reply other threads:[~2006-05-10 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 9:26 Sébastien Dugué [this message]
2006-05-10 10:08 ` Ingo Molnar
2006-05-10 13:03 ` Sébastien Dugué
2006-05-10 14:32 ` Thomas Gleixner
2006-05-10 15:01 ` Jakub Jelinek
2006-05-10 17:02 ` Thomas Gleixner
2006-05-11 8:56 ` Sébastien Dugué
2006-05-16 10:36 ` Jakub Jelinek
2006-05-18 8:51 ` Sébastien Dugué
2006-05-12 13:32 ` Pierre Peiffer
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=20060510112651.24a36e7b@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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