All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jonas Flodin <jonas.flodin@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Scheduler extensions
Date: Tue, 08 May 2012 11:10:56 +0200	[thread overview]
Message-ID: <4FA8E320.5070302@domain.hid> (raw)
In-Reply-To: <4FA8C9D6.4020404@domain.hid>

On 05/08/2012 09:23 AM, Jonas Flodin wrote:
>
> Hi!
>
> I'm a PhD student who is currently doing research on multicore real-time
> scheduling. I'm considering using Xenomai as a base for my research
> experiments, but this would require me to replace or extend the current
> scheduler. So far I have found no documents detailing how the scheduler
> is implemented or how to extend it (if possible). Could you point me to
> information regarding the scheduler?
>

There is no documentation on the scheduling core. You should probably 
start with ksrc/nucleus/sched*.c, and include/nucleus/sched*.h, having a 
look at the files implementing the plain FIFO policy in sched-rt*.

Hint: the scheduling core is meant to be extensible, adding a new policy 
entails providing an implementation for a new struct xnsched_class 
object. Make sure to read the comments in the files implementing the 
existing policies (-rt, -sporadic, -tp), they usually mention details on 
the calling context and requirements for the handlers defined by the 
xnsched_class type.

> Thank you in advance.
>
> BR
> Jonas Flodin
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
>


-- 
Philippe.


      reply	other threads:[~2012-05-08  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08  7:23 [Xenomai-core] Scheduler extensions Jonas Flodin
2012-05-08  9:10 ` Philippe Gerum [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=4FA8E320.5070302@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jonas.flodin@domain.hid \
    --cc=xenomai@xenomai.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.