I have some code that seems to work. Here's what it reports below. Does that look ok to you?
I had to modify quite a lot of things to make the parsing of /proc/cpuinfo more robust (the code is basically arch-specific now), so I am not sure we'll be able to backport this to OMPI.
* Sandy-Bridge Xeon E5 (Stampede)
CPUModel=Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
* Old Nehalem-EX
CPUModel=Intel(R) Xeon(R) CPU E7540 @ 2.00GHz
CPUModel=Dual-Core Intel(R) Itanium(R) Processor 9140N
CPUModel=Dual Core AMD Opteron(tm) Processor 865
* MIC (Stampede)
Le 23/01/2014 19:50, Ralph Castain a écrit :
> That would be perfect! Thanks
> On Jan 23, 2014, at 10:27 AM, Brice Goglin <Brice.Goglin_at_[hidden]> wrote:
>> Should be easy on Linux, sure.
>> The model name is already known as CPUModel in hwloc.
>> We should likely add CPUVendor (would be GenuineIntel or AuthenticAMD), CPUFamily (or CPUFamilyNumber if there's a name for these families?) and CPUModelNumber ?
>> Le 23/01/2014 19:09, Ralph Castain a écrit :
>>> Hi folks
>>> Looking at the current topology info, I see you capture the model name for the socket, but not a couple of other key things Intel could use:
>>> cpu family : 6
>>> model : 44
>>> model name : Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
>>> Both the cpu family and model are important to us - any issue with adding them to the "infos" array?
>>> hwloc-devel mailing list
>> hwloc-devel mailing list
> hwloc-devel mailing list
hwloc-devel mailing list