On 9/04/2014 4:09 pm, Sebastian Huber wrote:
On 2014-04-08 17:09, Jennifer Averett wrote:
I thought the consensus was that non-smp systems would not
support affinity methods.
I don't remember a discussion about this.
I think it makes it easier for application developers if the don't have
to plaster their code with #ifdef RTEMS_SMP. You should also be able to
write libraries that work with SMP and non-SMP configurations. For this
we have to provide the same ABI. This should be the long term goal.
I propose to add a new requirement:
The non-SMP and SMP RTEMS Classic API should be ABI compatible.
I agree with this. I feel in this case the an error should be returned
and the user can then decide what to do.
Does mean we need to add the support deeper into the score ? I would
assume keeping the support out of the layer below the API should help
keep the foot print down on uni-processor builds.
http://www.rtems.org/wiki/index.php?title=SMP#Requirements
On Linux you can use the thread affinity functions also on non-SMP systems.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
