From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <468D8AF1.2090400@wmipf.in-berlin.de>
Date: Fri,  6 Jul 2007 02:21:05 +0200
From: =?UTF-8?B?TWljaGFlbCBUZWljaGdyw6RiZXI=?= <mt@wmipf.in-berlin.de>
User-Agent: Icedove 1.5.0.8 (X11/20061208)
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [9fans] devrealtime
Topicbox-Message-UUID: 91c82aa0-ead2-11e9-9d60-3106f5b1d025

Hi,

I have just tried the realtime scheduler using `echo's of period, cost,
admit into the /proc/.../ctl of a test program.

In a 9fans posting I have seen another example where a real-time process
was created by opening /dev/realtime/clone. This usage pattern looks
interesting; a task that needs real-time conditions is not a real-time
task itself, but uses such a task to get the desired timing (this is at
least my understanding of it).

Apparently devrealtime.c has been removed from the kernel some time ago.
Likely this interface is obsolete, and the devproc one is current.

How would I use that properly? I suppose a task could write to its own
/proc/.../ctl to enable real-time mode. Is there an example available
similar to the devrealtime one?

Thanks,
Michael