[PATCH 1/8] score: Add CPU_MAXIMUM_PROCESSORS

[Joel Sherrill]

On Thu, Mar 3, 2016 at 9:12 AM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

>
>
> On 03/03/16 16:10, Joel Sherrill wrote:
>
>> How does this interact with the pthread affinity and cpuset size?
>>
>
> Its unrelated to the high level API.
>
>
>> If we end up with a port that can support more than 32, then do we
>> increase the cpuset size or make applications more to variable cpuset's?
>>
>
> No, the high level API is a different issue.
>
>
>> What's the intended use?
>>
>
> The high level API cpu_set_t is to inefficient for internal use. Linux
> uses something similar internally.


So the affinity data structure internally is going to change?

This constant was added for some purpose. What is it?

>
>
> --
> 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.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160303/acb4f9fd/attachment-0002.html>