Are the abstractions anything like Bernd's perl bindings, perchance?
http://search.cpan.org/~bka/
On Jan 17, 2011, at 3:02 PM, Guy Streeter wrote:
> I am currently working to get a public git repository set up so that I can
> share the work. In the meantime, my first pass at python binding
Hallo,
I'm using hwloc-1.1 on Linux 2.6.32.19 (x86_64) on a machine that has
several NUMA nodes. It seems to me that there are unwanted bits left in
the nodeset "set", when calling hwloc_get_membind_nodeset(topo,
set, ...) after a successful hwloc_set_membind() or
hwloc_set_membind_nodeset().
E.g
On 01/18/2011 06:47 AM, Jeff Squyres wrote:
Are the abstractions anything like Bernd's perl bindings, perchance?
http://search.cpan.org/~bka/
On Jan 17, 2011, at 3:02 PM, Guy Streeter wrote:
I am currently working to get a public git repository set up so that I can
share the work. In t
Le 18/01/2011 17:40, Bernd Kallies a écrit :
> Hallo,
>
> I'm using hwloc-1.1 on Linux 2.6.32.19 (x86_64) on a machine that has
> several NUMA nodes. It seems to me that there are unwanted bits left in
> the nodeset "set", when calling hwloc_get_membind_nodeset(topo,
> set, ...) after a successful
On Tue, 2011-01-18 at 19:11 +0100, Brice Goglin wrote:
> Le 18/01/2011 17:40, Bernd Kallies a écrit :
> > Hallo,
> >
> > I'm using hwloc-1.1 on Linux 2.6.32.19 (x86_64) on a machine that has
> > several NUMA nodes. It seems to me that there are unwanted bits left in
> > the nodeset "set", when call
On Jan 12, 2011, at 10:10 AM, Samuel Thibault wrote:
> This is not what I meant: hwloc_alloc_membind_policy's purpose is only
> to allocate bound memory. It happens that hwloc_alloc_membind_policy
> _may_ change the process policy in order to be able to bind memory
> at all (when the underlying OS
Le 18/01/2011 19:38, Bernd Kallies a écrit :
> max_os_index = 512, HWLOC_BITS_PER_LONG = 64, rounding gives
> max_os_index = 576.
>
> I also saw the same behaviour on a much smaller machine (usual 2-socket
> Nehalem-EP). CONFIG_NODES_SHIFT is not found in /proc/config.gz.
> max_os_index = 64, HWLOC
I took the liberty of committing this in r3090.
On Jan 18, 2011, at 2:00 PM, Jeff Squyres wrote:
> On Jan 12, 2011, at 10:10 AM, Samuel Thibault wrote:
>
>> This is not what I meant: hwloc_alloc_membind_policy's purpose is only
>> to allocate bound memory. It happens that hwloc_alloc_membind_pol
Jeff Squyres, le Tue 18 Jan 2011 20:00:42 +0100, a écrit :
> On Jan 12, 2011, at 10:10 AM, Samuel Thibault wrote:
> > This is not what I meant: hwloc_alloc_membind_policy's purpose is only
> > to allocate bound memory. It happens that hwloc_alloc_membind_policy
> > _may_ change the process policy i
Thanks for fixing it up!
On Jan 18, 2011, at 6:13 PM, Samuel Thibault wrote:
> Jeff Squyres, le Tue 18 Jan 2011 20:00:42 +0100, a écrit :
>> On Jan 12, 2011, at 10:10 AM, Samuel Thibault wrote:
>>> This is not what I meant: hwloc_alloc_membind_policy's purpose is only
>>> to allocate bound memory
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.2a1r3091
Start time: Tue Jan 18 21:01:04 EST 2011
End time: Tue Jan 18 21:03:34 EST 2011
Your friendly daemon,
Cyrador
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.1.1a1r3093
Start time: Tue Jan 18 21:03:34 EST 2011
End time: Tue Jan 18 21:06:01 EST 2011
Your friendly daemon,
Cyrador
12 matches
Mail list logo
