Jeff Squyres wrote:
> On May 16, 2007, at 8:40 AM, Bert Wesarg wrote:
>
>>> - Perhaps we should not use the type name cpuset_t since it is used
>>> for multiple different kinds of items (sockets, nodes, etc.). How
>>> about bitmap_t? E.g. (regardless of whatever the function names end
>>> up being):
>>>
>>> map_from_node_id(int node_id, plpa_bitmap_t *cpuset);
>>> get_node_set(plpa_bitmap_t *nodeset);
>>> ...etc.
>> Yes, this cpu-centric name bothered me too. But maybe bitmap_t
>> sounds to
>> generic, how is idset_t?
>
> Works for me. Wiki updated.
Next question: how many bits are needed, the default from the cpu_set_t is
1024, for big irons this is too few, for a 'small' system too much. When
we introduce this new type, we can specify the size and/or can make this
an configure option. this will limit the portability of a compiled
library, but reduce memory footprint on systems, where the admin knows
what he is doing. the linux kernel makes the same, per configure you
specify max number of supported cpus and max numbers of nodes, and the
kernel takes the roundup to the size of unsigned long.
Bert
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}