From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew <aathan-linux-kernel-1542@cloakmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
roland@topspin.com, Andrew Morton <akpm@osdl.org>
Subject: RE: Consistent lock up 2.6.10-rc1-bk7 (mutex/SCHED_RR bug?)
Date: Fri, 29 Oct 2004 16:07:02 +0100 [thread overview]
Message-ID: <1099062404.13098.59.camel@localhost.localdomain> (raw)
In-Reply-To: <OMEGLKPBDPDHAGCIBHHJOELLFCAA.aathan-linux-kernel-1542@cloakmail.com>
On Gwe, 2004-10-29 at 15:26, Andrew wrote:
> Although it appears I need to fix an applicaiton bug, is it normal/desirable for an application calling system mutex facilities to
> starve the system so completely, and/or become "unkillable"?
If it is SCHED_RR then it may get to hog the processor but it should not
be doing worse than that and should be killable by something higher
priority.
You are right to suspect futexes don't deal with hard real time but the
failure you see isnt the intended failure case.
[Inaky has posted some drafts of a near futex efficient lock system that
ought to work for real time use btw]
Alan
next prev parent reply other threads:[~2004-10-29 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OMEGLKPBDPDHAGCIBHHJMEIDFCAA.aathan-linux-kernel-1542@cloakmail.com>
2004-10-29 14:26 ` Consistent lock up 2.6.10-rc1-bk7 (mutex/SCHED_RR bug?) Andrew
2004-10-29 15:07 ` Alan Cox [this message]
2004-10-29 16:43 ` Andrew A.
2004-10-29 17:06 ` Chris Wright
2004-10-29 17:44 ` Andrew A.
2004-10-29 20:32 ` Chris Wright
2004-10-29 15:36 ` Andrew A.
2004-10-29 15:52 ` Andrew A.
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=1099062404.13098.59.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=aathan-linux-kernel-1542@cloakmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.com \
/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