From: "Chris Friesen" <cfriesen@nortel.com>
To: Jussi Laako <jussi@sonarnerd.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
James Courtier-Dutton <James@superbug.co.uk>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
d.faggioli@sssup.it
Subject: Re: [RFC][PATCH] Multimedia scheduling class, take 2
Date: Tue, 12 May 2009 09:32:00 -0600 [thread overview]
Message-ID: <4A099670.5060902@nortel.com> (raw)
In-Reply-To: <4A094707.5040307@sonarnerd.net>
Jussi Laako wrote:
> Peter Zijlstra wrote:
>
>>As to the patch, I still think its an exceedingly bad idea to create
>>such a horridly ill defined scheduler class. There's nothing that keeps
>>people from stuffing everything in there and either generating DoS
>>issues or still generating bad interactivity.
>
>
> Lite patch practically exports nice levels as scheduling priorities in
> order to make it possible to assign different levels to different
> threads of the same process.
If all you're trying to do is allow different threads to run at
different nice levels, what about extending sys_setpriority() to take a
"which" of PRIO_THREAD? We'd probably have to call the syscall directly
until/unless libc picks up the new option.
Chris
next prev parent reply other threads:[~2009-05-12 15:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 18:40 [RFC][PATCH] Multimedia scheduling class Jussi Laako
2008-12-30 7:42 ` Peter Zijlstra
2008-12-30 8:39 ` Jussi Laako
2009-01-12 9:55 ` Jussi Laako
2009-01-12 10:28 ` Peter Zijlstra
2009-01-13 9:44 ` Jussi Laako
2009-01-17 12:49 ` James Courtier-Dutton
2009-01-25 23:09 ` Jussi Laako
2009-01-26 7:25 ` Peter Zijlstra
2009-05-11 8:22 ` [RFC][PATCH] Multimedia scheduling class, take 2 Jussi Laako
2009-05-12 5:38 ` Artem Bityutskiy
2009-05-12 5:57 ` Peter Zijlstra
2009-05-12 9:53 ` Jussi Laako
2009-05-12 15:32 ` Chris Friesen [this message]
2009-05-12 16:34 ` Jussi Laako
2009-05-12 16:45 ` Raistlin
2009-05-12 17:38 ` Jussi Laako
2009-05-12 17:55 ` Jussi Laako
2009-05-12 17:00 ` Chris Friesen
2009-05-12 17:53 ` Jussi Laako
2009-05-12 23:04 ` Chris Friesen
2009-05-13 6:36 ` Jussi Laako
2009-05-12 10:07 ` Jussi Laako
2009-05-12 11:19 ` Peter Zijlstra
2009-05-12 12:12 ` Jussi Laako
2009-05-12 9:40 ` Henrik Austad
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=4A099670.5060902@nortel.com \
--to=cfriesen@nortel.com \
--cc=James@superbug.co.uk \
--cc=d.faggioli@sssup.it \
--cc=jussi@sonarnerd.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.