On 10/17/2012 01:28 PM, Arnout Vandecappelle wrote:
> Hoi,
>
> I noticed that when using the native skin, starting an application with
> "taskset 2 <my_app>" does not put the application on processor 2. Diving into
> the code, it turns out that calling rt_task_shadow() throws away the thread's
> cpuset,
That is an issue.
> and also rt_task_create() looks only at the mode parameter and ignores
> the parent thread's affinity.
That does not look like an issue. Why should a task inherit its parent's
affinity.
>
> Is this intentional? If yes, that means that using the native skin, there
> is no way to set a task's affinity except explicitly specifying T_CPU when
> the task is started, right?
No, this looks like a different issue.
>
> Note, by the way, that calling sched_setaffinity _after_ the task has
> started
> _will_ change the affinity (cfr. switchtest), but any calls _before_ the task
> has started are ignored.
Well, if the thread is not created, how sched_setaffinity change its
affinity?
--
Gilles.
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
