From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Ingo Molnar <mingo@elte.hu>
Cc: Florian Schmidt <mista.tapas@gmx.net>,
Michael Geithe <warpy@gmx.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-rc1-bk4 and kernel/futex.c:542
Date: Tue, 26 Oct 2004 19:21:24 +0200 [thread overview]
Message-ID: <417E8794.9040102@stud.feec.vutbr.cz> (raw)
In-Reply-To: <20041026112415.GA21015@elte.hu>
Ingo Molnar wrote:
> yeah, it definitely looks like there is some futex race that the
> PREEMPT_REALTIME kernel triggers in no time. (this is because the
> locking in the PREEMPT_REALTIME kernel is equivalent to an SMP system
> with an infinite number of CPUs and will trigger the same races.)
>
> Ingo
That's an interesting claim. I don't understand why it is equivalent.
Could you please explain it?
Michal
prev parent reply other threads:[~2004-10-26 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 9:35 2.6.10-rc1-bk4 and kernel/futex.c:542 Michael Geithe
2004-10-26 11:31 ` Florian Schmidt
2004-10-26 11:24 ` Ingo Molnar
2004-10-26 11:38 ` Michael Geithe
2004-10-26 12:04 ` Nick Piggin
2004-10-26 18:50 ` Ingo Molnar
2004-10-26 17:21 ` Michal Schmidt [this message]
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=417E8794.9040102@stud.feec.vutbr.cz \
--to=xschmi00@stud.feec.vutbr.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mista.tapas@gmx.net \
--cc=warpy@gmx.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.