From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: "Bill Huey (hui)" <bill.huey@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Cc: Dario Faggioli <raistlin@linux.it>,
Alessandro Zummo <a.zummo@towertech.it>,
Thomas Gleixner <tglx@linutronix.de>,
KY Srinivasan <kys@microsoft.com>,
Amir Frenkel <frenkel.amir@gmail.com>,
Bdale Garbee <bdale@gag.com>
Subject: Re: [PATCH RFC v0 00/12] Cyclic Scheduler Against RTC
Date: Tue, 12 Apr 2016 07:58:35 +0200 [thread overview]
Message-ID: <1460440715.3839.101.camel@gmail.com> (raw)
In-Reply-To: <1460438960-32060-1-git-send-email-bill.huey@gmail.com>
On Mon, 2016-04-11 at 22:29 -0700, Bill Huey (hui) wrote:
> Hi,
>
> This a crude cyclic scheduler implementation. It uses SCHED_FIFO tasks
> and runs them according to a map pattern specified by a 64 bit mask. Each
> bit corresponds to an entry into an 64 entry array of
> 'struct task_struct'. This works single core CPU 0 only for now.
>
> Threads are 'admitted' to this map by an extension to the ioctl() via the
> of (rtc) real-time clock interface. The bit pattern then determines when
> the task will run or activate next.
>
> The /dev/rtc interface is choosen for this purpose because of its
> accessibilty to userspace. For example, the mplayer program already use
> it as a timer source and could possibly benefit from being sync to a
> vertical retrace interrupt during decoding. Could be an OpenGL program
> needing precisely scheduler support for those same handling vertical
> retrace interrupts, low latency audio and timely handling of touch
> events amognst other uses.
Sounds like you want SGI's frame rate scheduler.
-Mike
next prev parent reply other threads:[~2016-04-12 5:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 5:29 [PATCH RFC v0 00/12] Cyclic Scheduler Against RTC Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 01/12] Kconfig change Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 02/12] Reroute rtc update irqs to the cyclic scheduler handler Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 03/12] Add cyclic support to rtc-dev.c Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 04/12] Anonymous struct initialization Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 05/12] Task tracking per file descriptor Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 06/12] Add anonymous struct to sched_rt_entity Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 07/12] kernel/userspace additions for addition ioctl() support for rtc Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 08/12] Compilation support Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 09/12] Add priority support for the cyclic scheduler Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 10/12] Export SCHED_FIFO/RT requeuing functions Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 11/12] Cyclic scheduler support Bill Huey (hui)
2016-04-12 5:29 ` [PATCH RFC v0 12/12] Cyclic/rtc documentation Bill Huey (hui)
2016-04-12 5:58 ` Mike Galbraith [this message]
[not found] ` <CAAmnkz=X4TtY7LQwPuWWD0q99XeZQT+53RZ_7dNb3P=X=+jxrg@mail.gmail.com>
2016-04-12 6:05 ` [PATCH RFC v0 00/12] Cyclic Scheduler Against RTC Mike Galbraith
2016-04-13 8:57 ` Juri Lelli
2016-04-13 9:37 ` Bill Huey (hui)
2016-04-13 10:08 ` Juri Lelli
2016-04-13 10:35 ` Bill Huey (hui)
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=1460440715.3839.101.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=a.zummo@towertech.it \
--cc=bdale@gag.com \
--cc=bill.huey@gmail.com \
--cc=frenkel.amir@gmail.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).