Michael Closson wrote:
> Hi Eric, et.al.,
>
> Sorry for the delay :p
>
> On 2/2/07, Eric Saxe <[EMAIL PROTECTED]> wrote:
>> For which versions of Solaris are you interested?
> That's still an open question. Say 2.5 and up. Since the info is
> mostly arch specific, I'm hoping that the detection method won't be
> unique for every combination of os_version and arch.
>
>
>> For sun4u systems, this information is generally encoded in the cpu id,
>> in a platform specific way.
>
> Did sun4u procs even support multicores/threads? If not, I can assume
> that whatever sysconfig(_SC_NPROCESSORS_CONF) returns is all physical
> procs.
What about UltraSPARC IV? They are dual core, aren't they?
>
>> For sun4v, as Dave said, the mappings are defined by a "machine
>> description" that the Hypervisor produces.
>>
>> For Niagara I, cpuid/4 will give you a core / instruction pipeline id.
>> Obviously that's very processor specific. :)
>
> Wow. I'm really just looking for a way to determine the number of
> cores per chip and the number of threads per core.
Except for US-IV, and Niagra of course, all Sun processors are single core.
>
> Right now I use kstat cpu_info and count the number of unique
> chip_id's and core_is's, and do the math.
I would think that would be a good way to do it.
-- Garrett
>
>
> Thanks for the help!
>
> Mike Closson
> _______________________________________________
> opensolaris-code mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
--
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134 Fax: 951 325-2191
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
