I see a flurry of windows-related activity over the weekend.
Do you guys want me to cut rc4?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Jeff Squyres, le Mon 03 May 2010 09:28:41 -0400, a écrit :
> I see a flurry of windows-related activity over the weekend.
>
> Do you guys want me to cut rc4?
I'm done with what I wanted to fix in rc3.
Samuel
1.0rc4 is up. Send me a windows binary when you get a chance.
On May 3, 2010, at 9:30 AM, Samuel Thibault wrote:
> Jeff Squyres, le Mon 03 May 2010 09:28:41 -0400, a écrit :
> > I see a flurry of windows-related activity over the weekend.
> >
> > Do you guys want me to cut rc4?
>
> I'm done wi
Jeff Squyres, le Mon 03 May 2010 09:57:09 -0400, a écrit :
> 1.0rc4 is up. Send me a windows binary when you get a chance.
http://dept-info.labri.fr/~thibault/tmp/hwloc-win32-build-1.0rc4.zip
Samuel
Posted.
On May 3, 2010, at 10:37 AM, Samuel Thibault wrote:
> Jeff Squyres, le Mon 03 May 2010 09:57:09 -0400, a écrit :
> > 1.0rc4 is up. Send me a windows binary when you get a chance.
>
> http://dept-info.labri.fr/~thibault/tmp/hwloc-win32-build-1.0rc4.zip
>
> Samuel
> _
Running lstopo on w7 (64 bit):
-
C:\Temp\hwloc>lstopo
Note: GetLogicalProcessorInformationEx was never tested yet!
-
Plus, the memory it reported was the currently free memory, not total memory.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.c
Jeff Squyres, le Mon 03 May 2010 15:57:37 -0500, a écrit :
> Running lstopo on w7 (64 bit):
>
> -
> C:\Temp\hwloc>lstopo
> Note: GetLogicalProcessorInformationEx was never tested yet!
> -
Ooops, it seems I have forgotten to remove it. Now done.
> Plus, the memory it reported was the curr
(I'm asking my local Microsoft contact)
On May 3, 2010, at 4:15 PM, Samuel Thibault wrote:
> Jeff Squyres, le Mon 03 May 2010 15:57:37 -0500, a écrit :
> > Running lstopo on w7 (64 bit):
> >
> > -
> > C:\Temp\hwloc>lstopo
> > Note: GetLogicalProcessorInformationEx was never tested yet!
>
He says:
GlobalMemoryStatusEx
http://msdn.microsoft.com/en-us/library/aa366589(v=VS.85).aspx
But that doesn't give numa node information. :-\
He's looking to see if he can find another function that gives numa info, but
it may take a little time (the windows memory subsystem guy is not availab
Is this helpful?
http://msdn.microsoft.com/en-us/library/ms724379(VS.85).aspx
You can use that to enumerate the ACPI firmware tables directly. Supposedly,
you should be able to discover topology information. Not very user friendly,
unfortunately.
On May 3, 2010, at 4:52 PM, Jeff Squyres
If this gives access to the SRAT table or things like that, it may give
us a lot of locality info (IIRC, that's what Linux reads to get NUMA and
I/O locality information). But I hope I won't be the one writing the
ACPI table parser :)
Brice
On 04/05/2010 00:09, Jeff Squyres wrote:
> Is this h
Brice Goglin, le Tue 04 May 2010 00:15:42 +0200, a écrit :
> If this gives access to the SRAT table or things like that, it may give
> us a lot of locality info (IIRC, that's what Linux reads to get NUMA and
> I/O locality information). But I hope I won't be the one writing the
> ACPI table parser
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.1a1r2040
Start time: Mon May 3 21:01:05 EDT 2010
End time: Mon May 3 21:03:01 EDT 2010
Your friendly daemon,
Cyrador
On 03/05/10 09:57, Jeff Squyres wrote:
> 1.0rc4 is up.
Running coccicheck on 1.0rc4 flags up this construct, I presume
as an ambiguous construction:
if (!topology->flags & HWLOC_TOPOLOGY_FLAG_WHOLE_SYSTEM) {
That's at line 1518 of src/topology.c in hwloc_discover(). The
check file simply sa
Awesome; thanks Chris!
On May 3, 2010, at 8:57 PM, Christopher Samuel wrote:
> On 03/05/10 09:57, Jeff Squyres wrote:
>
> > 1.0rc4 is up.
>
> Running coccicheck on 1.0rc4 flags up this construct, I presume
> as an ambiguous construction:
>
> if (!topology->flags & HWLOC_TOPOLOGY_FLAG_WHOLE
15 matches
Mail list logo
