public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: linuxquestasu@yahoo.com
Subject: Cyclic Scheduling for linux
Date: 31 Oct 2003 19:32:03 -0500	[thread overview]
Message-ID: <1067646722.2560.259.camel@cube> (raw)

> I am working on providing a cyclic scheduling policy
> to the current non real time version of the linux to
> support hard real time tasks as part of one of my
> projects. This policy should be able to support
> aperiodic, periodic and sporadic tasks too. Could any
> one pour some light on how to go about achieving it?.
>
> Any Helpful tips, project reports, links or advices
> are greatly appreciated.

I suppose you expect to write this, but if not,
you can get it in Concurrent's Red Hawk Linux
product.

Marketing says:

"RedHawk's Frequency-Based Scheduler (FBS) is a
high-resolution task scheduler that enables the
user to run processes in cyclical execution patterns.
FBS can control the periodic execution of multiple,
coordinated processes utilizing major and minor
cycles with overrun detection. A performance
monitor is also provided to view CPU utilization
during each scheduled execution frame."

That's on a "real" Linux kernel, not like RTAI
or RT-Linux. There are some other cool real-time
features as well, and an Ada compiler if you're
so inclined.



             reply	other threads:[~2003-11-01  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01  0:32 Albert Cahalan [this message]
2003-11-03 23:27 ` Cyclic Scheduling for linux George Anzinger
  -- strict thread matches above, loose matches on Subject: below --
2003-10-30 18:15 First Name
2003-10-30 21:01 ` George Anzinger

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=1067646722.2560.259.camel@cube \
    --to=albert@users.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxquestasu@yahoo.com \
    /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