From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Linked lists for userspace programs in Linux
Date: Mon, 16 Jun 2014 12:01:44 -0400 [thread overview]
Message-ID: <7216.1402934504@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 16 Jun 2014 21:35:20 +0800." <CAPAiGB8_oJ_wAHUw1nx0+xak6HXXKELyYboohdJo7KsYSU-Vzw@mail.gmail.com>
On Mon, 16 Jun 2014 21:35:20 +0800, Chandrasekaran Sivakumar said:
> Apologies from me. I didn't explain my problem properly. I am working on
> modifying the linux kernel's scheduler framework to include support for
> real-time algorithms. In order to give user inputs such as number of tasks,
> their execution cost, period, deadline etc, I am creating an userspace
> program. Then this program would transfer control to the kernel to perform
> system calls for creation and execution of tasks.
Nope. Wrong answer. You can't do real-time that way.
If the userspace code gets hung in a loop or something, your in-kernel
scheduler can get stuck with old/stale information, and as a result incorrectly
schedule the next process, causing a realtime window to be totally blown.
And if all the userspace code is doing is writing config information for
which tasks get what priorities, you should be instead extending the
sched_setscheduler() syscall, or possibly adding a /proc/PID/<something>
interface.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140616/ce988ee0/attachment.bin
prev parent reply other threads:[~2014-06-16 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 18:38 Linked lists for userspace programs in Linux Chandrasekaran Sivakumar
2014-06-16 3:24 ` Valdis.Kletnieks at vt.edu
2014-06-16 8:13 ` Robert P. J. Day
2014-06-16 13:35 ` Chandrasekaran Sivakumar
2014-06-16 16:01 ` Valdis.Kletnieks at vt.edu [this message]
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=7216.1402934504@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).