public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Benjamin LaHaise <bcrl@redhat.com>
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: 09 Dec 2001 18:21:05 -0500	[thread overview]
Message-ID: <1007940066.878.7.camel@phantasy> (raw)
In-Reply-To: <20011209181643.A8846@redhat.com>
In-Reply-To: <75F30A52-ECF4-11D5-80FE-00039355CFA6@suespammers.org> <1007939114.878.1.camel@phantasy>  <20011209181643.A8846@redhat.com>

On Sun, 2001-12-09 at 18:16, Benjamin LaHaise wrote:

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

But the point of a SCHED_IDLE would be to only run them while idle, so
they can still never even get the CPU.

Ahh ... wait, do you mean periodically run them, but only give them the
boost while they are in kernel space?  Very good idea.  Can you see an
easy way to do this?

	Robert Love


  reply	other threads:[~2001-12-09 23:21 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 [this message]
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=1007940066.878.7.camel@phantasy \
    --to=rml@tech9.net \
    --cc=asd@suespammers.org \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r6144@263.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox