All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Robert Love <rml@tech9.net>
Cc: Anthony DeRobertis <asd@suespammers.org>, root <r6144@263.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make highly niced processes run only when idle
Date: Sun, 9 Dec 2001 18:16:43 -0500	[thread overview]
Message-ID: <20011209181643.A8846@redhat.com> (raw)
In-Reply-To: <75F30A52-ECF4-11D5-80FE-00039355CFA6@suespammers.org> <1007939114.878.1.camel@phantasy>
In-Reply-To: <1007939114.878.1.camel@phantasy>; from rml@tech9.net on Sun, Dec 09, 2001 at 06:05:13PM -0500

On Sun, Dec 09, 2001 at 06:05:13PM -0500, Robert Love wrote:
> 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
> something B wants, boost A's priority temporarily to that of B's).  But
> that is probably overkill ... note to do any of these it is probably
> cleanest to make a SCHED_IDLE scheduling class.

Even better would be to keep the process at low priority while in userland 
and reverts to normal "nice" priority while in kernelspace.

		-ben

  reply	other threads:[~2001-12-09 23:17 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 [this message]
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
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=20011209181643.A8846@redhat.com \
    --to=bcrl@redhat.com \
    --cc=asd@suespammers.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r6144@263.net \
    --cc=rml@tech9.net \
    /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.