From: Jussi Laako <jussi@sonarnerd.net>
To: Raistlin <raistlin@linux.it>
Cc: Chris Friesen <cfriesen@nortel.com>,
Peter Zijlstra <peterz@infradead.org>,
James Courtier-Dutton <James@superbug.co.uk>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC][PATCH] Multimedia scheduling class, take 2
Date: Tue, 12 May 2009 20:55:45 +0300 [thread overview]
Message-ID: <4A09B821.8000604@sonarnerd.net> (raw)
In-Reply-To: <1242146758.4792.19.camel@Palantir>
Raistlin wrote:
> Well, I'm not sure I can see why, since nor a "SCHED_MM" scheduling
> policy, nor having priorities for SCHED_OTHER (different from nice
> levels) is _not_ POSIX compliant, is it?
By the way, why is SCHED_IDLE and SCHED_BATCH OK, but not SCHED_MM?
Or is it the name? How about SCHED_INTERACTIVE?
- Jussi
next prev parent reply other threads:[~2009-05-12 17:55 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
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 [this message]
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=4A09B821.8000604@sonarnerd.net \
--to=jussi@sonarnerd.net \
--cc=James@superbug.co.uk \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
/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.