From: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
To: juri.lelli@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: sched: SCHED_DEADLINE v6
Date: Sun, 04 Nov 2012 20:30:16 +0100 [thread overview]
Message-ID: <op.wm9kgqki6426ze@localhost.localdomain> (raw)
In-Reply-To: <op.wm9i6bu76426ze@localhost.localdomain>
Nobody knows? This is really obscure for an EDF patch. Making things a bit
more accessible should be a priority. I think a lot of enthusiasts would
like to have smooth control over stuff, without windows-jitter. If you can
do a robot arm, jitter-free with this, then I am very interested.
uwaysi@Millennium:~/Kildekode/sched_deadline-schedtool-dl$ ./schedtool -E
-t 500:1000 3718
ERROR: could not set PID 3718 to E: SCHED_DEADLINE - Function not
implemented
uwaysi@Millennium:~/Kildekode/sched_deadline-schedtool-dl$
On Sun, 04 Nov 2012 20:02:25 +0100, Uwaysi Bin Kareem
<uwaysi.bin.kareem@paradoxuncreated.com> wrote:
> How does the modified schedtool work? There is no updated documentation.
>
> http://gitorious.org/sched_deadline/schedtool-dl/commits/latest/2.6.36-dl-V3
>
> If anyone could give an example of a 1000uS period / 500uS time, with
> schedtool, or any other relevant information.
> Most examples online use parameters that are no longer supported.
>
> Peace Be With You.
next prev parent reply other threads:[~2012-11-04 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 16:32 sched: SCHED_DEADLINE v6 Uwaysi Bin Kareem
2012-11-04 18:00 ` Uwaysi Bin Kareem
2012-11-04 19:02 ` Uwaysi Bin Kareem
2012-11-04 19:13 ` Uwaysi Bin Kareem
2012-11-04 19:30 ` Uwaysi Bin Kareem [this message]
[not found] <k2boS-2q4-11@gated-at.bofh.it>
[not found] ` <k2dK1-5rL-11@gated-at.bofh.it>
[not found] ` <k2ewr-6bR-15@gated-at.bofh.it>
[not found] ` <5098204D.3080002@onlinehome.de>
2012-11-05 20:34 ` Ove Karlsen
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=op.wm9kgqki6426ze@localhost.localdomain \
--to=uwaysi.bin.kareem@paradoxuncreated.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.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.