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 17:04:09 -0600 [thread overview]
Message-ID: <4A0A0069.4090502@nortel.com> (raw)
In-Reply-To: <4A09B7A1.2060706@sonarnerd.net>
Jussi Laako wrote:
> Chris Friesen wrote:
>
>>Of course, without glibc/pthreads support you would only be able to set
>>the nice level for the current thread since you don't have any way to
>>map from "pthread_t *" to tid. And you wouldn't be able to create new
>>threads with a particular nice level already set.
>
>
> This is the problem... It has to work this way, otherwise it's pretty
> useless.
Then you're hooped, because glibc checks for scheduler policies it
"knows" about.
>>But that argument
>>holds true for a new sched policy as well, because glibc checks the
>>policy internally and only knows about the normal three.
>
>
> Don't tell that to my system, where also SCHED_IDLE, SCHED_BATCH (which
> are btw not listed on POSIX either) ...and... SCHED_MM work. It goes
> directly to kernel which does the checks and fails if it sees fit.
Really? You can call pthread_attr_setschedpolicy() with a policy of
SCHED_MM? On my copy of glibc 2.8 it explicitly checks for
FIFO/RR/OTHER and anything else is rejected.
Chris
next prev parent reply other threads:[~2009-05-12 23:04 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
2009-05-12 17:00 ` Chris Friesen
2009-05-12 17:53 ` Jussi Laako
2009-05-12 23:04 ` Chris Friesen [this message]
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=4A0A0069.4090502@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.