Ravenscar and run-time program parameters

[Maciej Sobczak <see.my.homepage@gmail.com>]

As I understand, the Ravenscar profile forbids dynamically created
tasks - all tasks have to be created at the library level.

Consider a system where a (sub)set of tasks forms a task pool.
Depending on the actual deployment, it might make sense to influence
the size of this pool - in other words to influence the number of
tasks that are started within the system.

One obvious way to pass the requested number of tasks is to use
program parameters.

I don't see how this can be implemented within the constraint that all
tasks have to be created at the library level.

On the other hand, having a pool of tasks is often associated with the
pattern where the set of tasks wait on a *single* job queue (or
something conceptually equivalent) - and Max_Entry_Queue_Length=>1
would make such scenario more difficult to implement. I can still
imagine the set of tasks having their own queues, though.

How to parameterize the number of tasks in the Ravenscar-compliant
system?

--
Maciej Sobczak
http://www.msobczak.com/