This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: eCos scheduler
- From: Fabian Scheler <fabian dot scheler at gmail dot com>
- To: "gerardo dot rossi at studenti dot univr dot it" <gerardo dot rossi at studenti dot univr dot it>
- Cc: ecos-discuss at sourceware dot org, mirkomassi at tiscali dot it
- Date: Wed, 9 Nov 2005 17:33:47 +0100
- Subject: Re: [ECOS] eCos scheduler
- References: <20051109170218.vyebwhxswvs0k008@mail.studenti.univr.it>
Hello,
this topic has already been discussed here:
http://sourceware.org/ml/ecos-discuss/2005-10/msg00159.html
maybe the arguments announced there can help you
some comments:
- to implement the EDF scheduler on top of the bitmap scheduler is a
rather poor solution (as is to use the mlq-scheduler), how would you
handle more than 32 Threads with different priorities?
- you should implement a priority queue that is able to distinguish an
arbitrary number of different priorities t.m. deadlines (something
like a heap)
- about redirecting the calls: it is not that easy to 'redirect' the
calls, each scheduler has one scheduler specific class
Cyg_Scheduler_Implementation, if you want your EDF scheduler to be the
'standard' scheduler and want to use the bitmap scheduler as base,
then you have at least to rename the class
Cyg_Scheduler_Implementation implementing the bitmap scheduler
- if you make up your mind about the scheduleability of you system
before runtime you can maybe omit the thread attributes wcet and
period
Ciao, Fabian
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss