From: Pavel Machek <pavel@suse.cz>
To: Robert Love <rml@tech9.net>
Cc: Ton Hospel <linux-kernel@ton.iguana.be>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make highly niced processes run only when idle
Date: Thu, 13 Dec 2001 22:42:25 +0100 [thread overview]
Message-ID: <20011213224225.B129@elf.ucw.cz> (raw)
In-Reply-To: <75F30A52-ECF4-11D5-80FE-00039355CFA6@suespammers.org> <1007939114.878.1.camel@phantasy> <9v3nvj$a99$1@post.home.lunix> <1008035682.4287.3.camel@phantasy>
In-Reply-To: <1008035682.4287.3.camel@phantasy>
Hi!
> > 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).
>
> I agree, I said it was overkill.
>
> My solution is going to be to schedule the task as a SCHED_OTHER task
> when in the kernel, and as SCHED_IDLE task otherwise.
Yep, and you can do it without making syscalls any slower, and patch
was already on l-k.
Use ptrace-hooks for branching into your priority-promoting code, and
you'll have 0 impact on fast path.
Pavel
--
"I do not steal MS software. It is not worth it."
-- Pavel Kankovsky
prev parent reply other threads:[~2001-12-19 20:15 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
2001-12-11 1:54 ` Robert Love
2001-12-13 21:42 ` Pavel Machek [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=20011213224225.B129@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@ton.iguana.be \
--cc=linux-kernel@vger.kernel.org \
--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.