From: Ulrich Drepper <drepper@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: inaky.perez-gonzalez@intel.com, linux-kernel@vger.kernel.org,
robustmutexes@lists.osdl.org, rusty@rustcorp.com.au,
mingo@elte.hu, jamie@shareable.org
Subject: Re: [RFC/PATCH] FUSYN Realtime & robust mutexes for Linux, v2.3.1
Date: Thu, 05 Aug 2004 01:22:09 -0700 [thread overview]
Message-ID: <4111EE31.1090105@redhat.com> (raw)
In-Reply-To: <20040805004023.65463e88.akpm@osdl.org>
Andrew Morton wrote:
> But doesn't the current futex code continue to work unchanged?
If the patches don't touch the existing futex code there is no risk of
breaking anything. Futexes and these new objects have nothing to do
with each other.
> I was referring to "scheduling-policy based unlock/wakeup", actually.
We don't have anything like this for futexes. It's not impossible to
do, we just didn't do it because it was of not much interest to us at
that time.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
next prev parent reply other threads:[~2004-08-05 8:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 9:13 [RFC/PATCH] FUSYN Realtime & robust mutexes for Linux, v2.3.1 Perez-Gonzalez, Inaky
2004-08-05 6:21 ` Andrew Morton
2004-08-05 7:06 ` Ulrich Drepper
2004-08-05 7:17 ` Andrew Morton
2004-08-05 7:37 ` Ulrich Drepper
2004-08-05 7:40 ` Andrew Morton
2004-08-05 8:22 ` Ulrich Drepper [this message]
2004-08-05 10:42 ` Ingo Molnar
2004-08-05 11:48 ` Rusty Russell
2004-08-05 13:23 ` Linh Dang
2004-08-05 13:26 ` Linh Dang
2004-08-05 14:02 ` Chris Friesen
2004-08-05 10:34 ` Ingo Molnar
2004-08-05 10:59 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 8:39 Eric Valette
2004-08-05 18:16 Perez-Gonzalez, Inaky
2004-08-05 18:16 Perez-Gonzalez, Inaky
2004-08-05 18:16 Perez-Gonzalez, Inaky
2004-08-05 18:22 Perez-Gonzalez, Inaky
2004-08-05 18:37 Perez-Gonzalez, Inaky
2004-08-05 18:39 Perez-Gonzalez, Inaky
2004-08-05 18:39 Perez-Gonzalez, Inaky
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=4111EE31.1090105@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@osdl.org \
--cc=inaky.perez-gonzalez@intel.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robustmutexes@lists.osdl.org \
--cc=rusty@rustcorp.com.au \
/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