From: linux-kernel@ton.iguana.be (Ton Hospel)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make highly niced processes run only when idle
Date: Tue, 11 Dec 2001 01:36:51 +0000 (UTC) [thread overview]
Message-ID: <9v3nvj$a99$1@post.home.lunix> (raw)
In-Reply-To: <75F30A52-ECF4-11D5-80FE-00039355CFA6@suespammers.org> <1007939114.878.1.camel@phantasy>
In article <1007939114.878.1.camel@phantasy>,
Robert Love <rml@tech9.net> writes:
> I've seen a few solutions. The easiest is to just give idle tasks a
> "boost" on occasion to give them a chance to prevent the deadlock. You
> then, however, have the problem where the tasks can take advantage of
> the boost... Or, we could fix in-kernel deadlocks by doing priority
> inheriting on locks held by A and wanted by B (i.e., if A holds
Please don't. Whenever you think you priority inheritance, it's a sign your
system has got too complicated. The simplest solution is to simply have no
priorities when a task is in-kernel (or at least non that can completely
exclude a task).
next prev parent reply other threads:[~2001-12-11 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 4:38 [PATCH] Make highly niced processes run only when idle root
2001-12-08 4:39 ` Robert Love
2001-12-09 22:31 ` Anthony DeRobertis
2001-12-09 23:05 ` Robert Love
2001-12-09 23:16 ` Benjamin LaHaise
2001-12-09 23:21 ` Robert Love
2001-12-09 23:46 ` Benjamin LaHaise
2001-12-10 0:30 ` Robert Love
2001-12-10 2:46 ` Rik van Riel
2001-12-10 12:25 ` Niteshadow
2001-12-11 1:35 ` Steve Bergman
2001-12-19 23:49 ` Pavel Machek
2001-12-11 1:36 ` Ton Hospel [this message]
2001-12-11 1:54 ` Robert Love
2001-12-13 21:42 ` Pavel Machek
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='9v3nvj$a99$1@post.home.lunix' \
--to=linux-kernel@ton.iguana.be \
--cc=linux-kernel@vger.kernel.org \
/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.