From: Arjan van de Ven <arjan@infradead.org>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH] sched: Add SCHED_BGND (background) scheduling policy
Date: Wed, 05 Jul 2006 10:15:28 +0200 [thread overview]
Message-ID: <1152087328.3201.8.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <44AB726B.8070602@bigpond.net.au>
>
> Of course, a comprehensive (as opposed to RT only) priority inheritance
> mechanism would make the "safe/unsafe to background" problem go away and
> make this patch very simple. Any plans in that direction?
there is a very simple prio inheritance mechanism available already:
just treat "running in kernel mode" as a "go to nice +19" thing, and I
suspect things will suddenly be safe ;)
next prev parent reply other threads:[~2006-07-05 8:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 23:35 Peter Williams
2006-07-05 0:14 ` Con Kolivas
2006-07-05 0:49 ` Peter Williams
2006-07-05 0:52 ` Con Kolivas
2006-07-05 8:05 ` Andreas Mohr
2006-07-05 14:04 ` Jan Engelhardt
2006-07-05 0:44 ` Con Kolivas
2006-07-05 1:15 ` Peter Williams
2006-07-05 1:33 ` Con Kolivas
2006-07-05 4:20 ` Valdis.Kletnieks
2006-07-05 3:06 ` Peter Williams
2006-07-05 6:35 ` Ingo Molnar
2006-07-05 8:03 ` Peter Williams
2006-07-05 8:15 ` Arjan van de Ven [this message]
2006-07-05 8:19 ` Ingo Molnar
2006-07-05 17:40 ` Nick Piggin
2006-07-05 11:42 ` Mike Galbraith
2006-07-05 13:59 ` Peter Williams
2006-07-05 14:18 ` Peter Williams
2006-07-05 14:48 ` Mike Galbraith
2006-07-06 23:50 ` Peter Williams
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=1152087328.3201.8.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
/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
all inboxes | Powered by JetHome®