Scheduler in SMP
Matias Vara
matiasevara at gmail.com
Sat Sep 29 10:42:55 UTC 2012
2012/9/28 Joel Sherrill <joel.sherrill at oarcorp.com>
> On 09/28/2012 02:28 PM, Matias Vara wrote:
>
>> Hi everyone,
>>
>> I am playing with the samples of RTEMS for SMP. I am trying understand
>> the example in /smp01, this one creates one task per processor but I cannot
>> figure out how the task is set in a given processor. Are there any
>> parameter when the task is created?
>>
>>
>> This would be called task processor affinity and it is not currently
> supported. It was left as a future enhancement.
>
> The current smptests were not designed to show off smp but to
> debug it and to get coverage.
>
> The magic of assigning a task to a core is in the scheduler. It is
> in cpukit/score/src/**schedulersimplesmp*. It is logically intended to
> be the same as the single core scheduler but place the top N
> tasks onto the N cores. It takes into account priority, preemption,
> FIFO per priority, and timeslicing just like the single core priority
> scheduler does.
>
>
It is clear now, thanks for the answer!
Following the subject, then there is a one queue of task per processor? The
tasks are queued at the running time (when task_create is invoked)? If
they're queued at running time I suppose the access to such queue is
atomic.
Thanks in advance, Matias.
--
MV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120929/8f174afb/attachment-0001.html>
More information about the devel
mailing list