Le 26/10/2012 09:39, Brice Goglin a écrit :
> Le 26/10/2012 05:22, Robin Scher a écrit :
>> I would love to get this by my next release, say in the next 3-6
>> months. Is that something that would be possible? Is there anything I
>> can do to help?
>
> We'll have a v1.6 release before the end of th
Olivier Cessenat, le Sat 27 Oct 2012 19:10:55 +0200, a écrit :
> Just in case, I also provide the output of sysctl hw:
Thanks. There is indeed no package information (hw.packages), that's why
hwloc does not include any socket object.
Brice wrote:
> One way to solve this problem (which may also oc
Hello,
Sorry for not replying to your thread but my free zimbra box is broken
so I fetched your answer from
http://www.open-mpi.org/community/lists/hwloc-users/2012/10/0754.php
Please include my orange box if you reply so that I get the answer
instantly...
So, here is the output:
mac:/tmp/hwloc-1
Can you send your lstopo output?
preferably with latest trunk tarball
http://www.open-mpi.org/software/hwloc/nightly/trunk/hwloc-1.6a1r4928.tar.gz
One way to solve this problem (which may also occur on old Linux
distribs) would be to store the CPU model in the machine object. But
we'll have to ma
Hello,
Robin Scher indicated how to get the info on a Mac.
At least on mine (OSX 10.4) with darwin 8.11.1
where
$ sysctl -a machdep.cpu.brand_string
machdep.cpu.brand_string: Intel(R) Core(TM)2 CPU T7400 @
2.16GHz
I unfortunately have no socket:
*** The number of sockets is unknown
[ fro
Le 26/10/2012 05:22, Robin Scher a écrit :
> I would love to get this by my next release, say in the next 3-6
> months. Is that something that would be possible? Is there anything I
> can do to help?
We'll have a v1.6 release before the end of the year, and hopefully a
first release candidate by m
On 10/25/2012 3:06 PM, Samuel Thibault wrote:
Robin Scher, le Thu 25 Oct 2012 23:57:38 +0200, a écrit :
Do you think those could be added to hwloc?
Yes: we already use cpuid for the x86 backend. That will only work on
x86 hosts of course.
Windows being x86 only for the time being, I'm OK wit
Robin Scher, le Thu 25 Oct 2012 23:57:38 +0200, a écrit :
> ; eax = 0x8002 --> eax, ebx, ecx, edx: get processor name string
> (part 1)
> mov eax,0x8002
> cpuid
Oh, this is indeed *exactly* the model name string. I only knew about
the vendor_id string.
> I don't kn
Le 25/10/2012 23:57, Robin Scher a écrit :
> On OS-X, you can get this string from the sysctlbyname() call:
>
> const char *name = "machdep.cpu.brand_string";
> char buffer[ 64 ];
> size_t size = 64;
> if( !sysctlbyname( name, buffer, &size, NULL, 0 ) )
> memcpy( cpu_model,
Le 25/10/2012 23:42, Samuel Thibault a écrit :
> Robin Scher, le Thu 25 Oct 2012 23:39:46 +0200, a écrit :
>> Is there a way to get this string (e.g. "Intel(R) Core(TM) i7 CPU M 620 @
>> 2.67GHz") consistently on Windows, Linux, OS-X and Solaris?
> Currently, no.
>
> hwloc itself does not have a ta
On OS-X, you can get this string from the sysctlbyname() call:
const char *name = "machdep.cpu.brand_string";
char buffer[ 64 ];
size_t size = 64;
if( !sysctlbyname( name, buffer, &size, NULL, 0 ) )
memcpy( cpu_model, buffer, 12 * sizeof( int ) );
if That doesn't work, yo
Robin Scher, le Thu 25 Oct 2012 23:39:46 +0200, a écrit :
> Is there a way to get this string (e.g. "Intel(R) Core(TM) i7 CPU M 620 @
> 2.67GHz") consistently on Windows, Linux, OS-X and Solaris?
Currently, no.
hwloc itself does not have a table of such strings, and each OS has its
own table.
Sa
Hello,
Assuming you found the socket hwloc object whose name you want, do
hwloc_obj_get_info_by_name(obj, "CPUModel");
you'll get const char * pointing to what you want.
However, this info is only available on Linux and Solaris for now. If
you have any idea of to discover such info on other O
13 matches
Mail list logo
