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.
Le 04/01/2011 12:50, Bernd Kallies a écrit :
> Dear all,
> the current bitmap API of hwloc 1.1 supports input/output for bitmaps
> using strings that represent a map as hex words. The functions are
> hwloc_bitmap_snprintf, hwloc_bitmap_sscanf and the like.
> Linux cpusets in addition support an "ASCII list representation" of
> bitmaps, like 0-15,32-47. This is much easier to read and to write.
> I suggest to add corresponding functions to the hwloc bitmap C API.
Right, this has been in the TODO list for a while, I haven't had time to
work on it yet.
> Note that there also exists libcpuset and libbitmask in some Linux
> distributions. These are originally from SGI. There exist the functions
> bitmask_displayhex, bitmask_displaylist, bitmask_parsehex,
Both are LGPL unfortunately, we can't use this in hwloc (BSD).
> I added something like that to the most recent Sys::Hwloc Perl wrapper,
> which is currently found at
> The code for list input/output of hwloc bitmaps was adapted from recent
> linux kernel code, see e.g.
> (functions bitmap_scnlistprintf, bitmap_parselist).
This is GPL as well.
The code isn't hard to write anyway, I'll try to do it for 1.2. I guess
it would be hwloc_bitmap_list_snprintf/sscanf (we already have
hwloc_bitmap_taskset_snprintf/sccanf for taskset format printing/parsing).