Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [hwloc-devel] release status
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2009-10-05 12:07:48

On Oct 5, 2009, at 10:34 AM, Brice Goglin wrote:

> I haven't had time to actually fully implement this yet, but my last
> plan was opaque pointer + functions such as:
> hwloc_cpuset_t hwloc_cpuset_alloc(void);
> void hwloc_cpuset_destroy(hwloc_cpuset_t cpuset);

Minor quibble: it might be good to have nice "opposites" in the verbs
-- alloc and free, create and destroy, etc.

> hwloc_cpuset_t hwloc_cpuset_copy(hwloc_cpuset_t cpuset);
> with
> typedef struct hwloc_cpuset_s * hwloc_cpuset_t;

I like having the concept of a fully opaque pointer such that users
will be compelled to use the alloc/free functions.

Jeff Squyres