Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.0a1r1847
Start time: Mon Mar 22 21:01:01 EDT 2010
End time: Mon Mar 22 21:03:03 EDT 2010
Your friendly daemon,
Cyrador
On Mon, Mar 22, 2010 at 23:12, Brice Goglin wrote:
> Bert Wesarg wrote:
> I would also rename hwloc_cpuset_clearset() to
> hwloc_cpuset_andnotset(), so it fits to the _{or,and,xor,not}set
> naming style (i.e. they are named after the bit operation).
>
I don't like andnotset()
Bert Wesarg wrote:
I would also rename hwloc_cpuset_clearset() to
hwloc_cpuset_andnotset(), so it fits to the _{or,and,xor,not}set
naming style (i.e. they are named after the bit operation).
>>> I don't like andnotset() at all, sorry.
>>>
>> We could add an alias
On Mon, Mar 22, 2010 at 22:44, Samuel Thibault wrote:
> Brice Goglin, le Mon 22 Mar 2010 22:37:59 +0100, a écrit :
>> Bert Wesarg wrote:
>> > In case of the
>> > binary cpuset operations I find the ' = op ' style
>> > more flexible, than the current ' op= ' style.
>>
>> Given that you don't like
Brice Goglin, le Mon 22 Mar 2010 22:37:59 +0100, a écrit :
> Bert Wesarg wrote:
> > In case of the
> > binary cpuset operations I find the ' = op ' style
> > more flexible, than the current ' op= ' style.
>
> Given that you don't like malloc, you really don't want this :)
I guess he meant
hwloc
Bert Wesarg wrote:
> In case of the
> binary cpuset operations I find the ' = op ' style
> more flexible, than the current ' op= ' style.
Given that you don't like malloc, you really don't want this :) Your
proposal would allocate a new cpuset for each operation. Given how many
"and" or "or" oper
On Mon, Mar 22, 2010 at 21:49, Jeff Squyres wrote:
> On Mar 22, 2010, at 4:34 PM, Bert Wesarg wrote:
>
>> > Same question again :)
>>
>> I suspect, I can't propose API changes after that, right? ;-)
>
> It would be good, yes. :-)
>
> Have you had a good look around hwloc? I.e., do you have a fee
On Mar 22, 2010, at 4:34 PM, Bert Wesarg wrote:
> > Same question again :)
>
> I suspect, I can't propose API changes after that, right? ;-)
It would be good, yes. :-)
Have you had a good look around hwloc? I.e., do you have a feel for whether
you will be suggesting any more API changes?
--
On Mon, Mar 22, 2010 at 21:29, Brice Goglin wrote:
> Brice Goglin wrote:
>> Are we doing a 1.0-rc1 soon ?
>>
>
> Same question again :)
I suspect, I can't propose API changes after that, right? ;-)
Bert
>
> Brice
>
Brice Goglin wrote:
> Are we doing a 1.0-rc1 soon ?
>
Same question again :)
Brice
Bert Wesarg, le Mon 22 Mar 2010 12:20:58 +0100, a écrit :
> > -static hwloc_cpuset_t
> > -hwloc_aix_get_thisproc_cpubind(hwloc_topology_t topology, int policy)
> > +static int
> > +hwloc_aix_get_thisproc_cpubind(hwloc_topology_t topology, hwloc_cpuset_t
> > hwloc_set, int policy)
> > {
> > rsid
On Mon, Mar 22, 2010 at 11:20, wrote:
> Author: sthibaul
> Date: 2010-03-22 06:20:31 EDT (Mon, 22 Mar 2010)
> New Revision: 1840
> URL: https://svn.open-mpi.org/trac/hwloc/changeset/1840
>
> Modified: trunk/src/topology-aix.c
> =
Brice Goglin, le Mon 22 Mar 2010 11:43:10 +0100, a écrit :
> Samuel Thibault wrote:
> > Bert Wesarg, le Sun 21 Mar 2010 13:31:14 +0100, a écrit :
> >> I would like to propose an interface change for these function, so
> >> that the caller provide the to-be-filled cpuset, to reduce the
> >> alloc/fr
On Mon, Mar 22, 2010 at 11:21, Samuel Thibault wrote:
> Bert Wesarg, le Sun 21 Mar 2010 13:31:14 +0100, a écrit :
>> I would like to propose an interface change for these function, so
>> that the caller provide the to-be-filled cpuset, to reduce the
>> alloc/free frequency.
>
> This is indeed bett
Samuel Thibault wrote:
> Bert Wesarg, le Sun 21 Mar 2010 13:31:14 +0100, a écrit :
>
>> I would like to propose an interface change for these function, so
>> that the caller provide the to-be-filled cpuset, to reduce the
>> alloc/free frequency.
>>
>
> This is indeed better (and actually re
Bert Wesarg, le Sun 21 Mar 2010 13:31:14 +0100, a écrit :
> I would like to propose an interface change for these function, so
> that the caller provide the to-be-filled cpuset, to reduce the
> alloc/free frequency.
This is indeed better (and actually reduces the amount of code in
hwloc), I have i
16 matches
Mail list logo
