From: Artem Bityutskiy <dedekind@yandex.ru>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jussi Laako <jussi@sonarnerd.net>,
Peter Zijlstra <peterz@infradead.org>,
James Courtier-Dutton <James@superbug.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Multimedia scheduling class, take 2
Date: Tue, 12 May 2009 08:38:26 +0300 [thread overview]
Message-ID: <4A090B52.7040301@yandex.ru> (raw)
In-Reply-To: <4A07E044.8040807@sonarnerd.net>
Jussi Laako wrote:
> Peter Zijlstra wrote:
>> Right, and I think the solution to this problem is twofold, 1)
>> application writers should start writing (soft) realtime applications if
>> they want (soft) realtime behaviour -- there's just no way around that.
>
> Just to avoid need for reviewing and reworking ~800 klocs of user space
> code in just gstreamer, here's a second take on patches. This time
> splitting things into smaller pieces. Attached patch exposes 40
> priorities ~ nice values as something accessible through
> sched_()/pthreads API in order to control priorities of individual
> threads. Current Linux implementation of SCHED_OTHER is broken in a way,
> that it exposes only one single priority level - 0. Thus no possibility
> to properly control priorities of threads through pthread API. This is
> patch is against 2.6.29.2 and not tested, but builds. I can also send
> rest of the changes as separate small feature patches as needed.
> However, before doing any more work I would like to hear opinions on
> this and especially what is wrong with the code or idea...
Ingo,
would it be possible to comment on this?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-05-12 5:39 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 [this message]
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
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=4A090B52.7040301@yandex.ru \
--to=dedekind@yandex.ru \
--cc=James@superbug.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox