This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
One thing we weren't so sure about while designing libtopology was
whether to use fixed-size cpuset_t or dynamic-size cpuset_t. The
advantage of the former is simplicity of course. The currently defined
size is 1024 cpus and can easily be configured if one needs more. We
could think that 1024 is plenty for now and we'll see later. But if
later we realize that we have to change the API in order to be able to
use dynamic-size cpuset_t (e.g. copy & destroy functions at least), that
will be a burden. Also, dynamic-size cpuset_t is actually more efficient
for small boxes for most operations, as the bitmask will be smaller.
While we are at libtopology->hwloc API transition and now that a few
people are subscribed to hwloc-devel, what do people think about it?
Maybe we should at least make sure that the API doesn't hinder potential
for dynamic support?