On 16/03/16 22:11, Chris Johns wrote:
On 16/03/2016 23:01, Darshit Shah wrote:
I have updated my draft proposal with a basic timeline for things that
need to be done. The link is shared on the tracking page and has been
submitted via the program website as well. I'm sharing it here as well:
https://goo.gl/UmgS61

Since this is a draft proposal, it may not be completely polished yet.
I'd appreciate any comments on it, especially the project description
and timeline.


" POSIX mandated processor affinityAPI"

This is actually not defined in POSIX. Its a non-portable Linux/BSD extension.

"schedulable task sets would miss their deadlines since it does not consider migrating high priority tasks"

I think this is not correct. The current APA scheduler should implement strong APA. However, it may iterate several times over all (!) ready tasks. This is the actual problem.

I would use the name "APA" for the new scheduler, e.g. schedulerapasmp.c.

We already have a ticket for this work:

https://devel.rtems.org/ticket/2510

With respect to the tests. In addition to worst case task sets, we have to define task sets that cover the basic operations and the corner cases. I suggest to use test driven development once the data structures and algorithm is clear. Start with a simple test and implement everything so that this test passes. Continue until everything is fine.


Looking good.

Could you please add something about the method of testing you plan to use? Not the tests just the set up details, eg is this with the scheduler simulator, qemu, or real hardware or all listed plus also which architectures?

We can use Qemu and the hardware here in our office.

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to