[lug] cpuinfo shows hyperthreading enabled, but no hyperthreading seen

Andrew Hoffman sixgod at gmail.com
Fri Oct 12 16:23:45 MDT 2012


What you probably need to find out is the processor model and system model
and make sure the MB directly supports HT.
-Andy

On Fri, Oct 12, 2012 at 5:11 PM, Michael Hirsch <mdhirsch at gmail.com> wrote:

> I haven't tried that.  This system isn't exactly a cluster, and I'm not
> sure if the CPU supports it.  But it is an interesting tool I hadn't known
> about.
>
> I'm just trying to figure out why hyperthreading seems to be supported,
> but isn't being used.  The real solution to our problem is to by a faster
> machine with faster hard drives, but I'd like to know the answer to the
> hyperthreading question.
>
> Thanks,
>
> Michael
>
>
> On Fri, Oct 12, 2012 at 2:11 PM, Davide Del Vento <
> davide.del.vento at gmail.com> wrote:
>
>> Have you tried this
>>
>> http://software.intel.com/en-us/articles/using-enhanced-intel-speedstep-features-in-hpc-clusters
>> ?
>>
>> On Fri, Oct 12, 2012 at 1:45 PM, Michael Hirsch <mdhirsch at gmail.com>
>> wrote:
>> > I have server with a single quad-core cpu.  It's a kinda old Xeon, and
>> we'd
>> > like to get the most out of it.  I had thought that it was a dual-core
>> with
>> > hyperthreading, but a bit more research shows that it is a quad-core
>> with no
>> > hyperthreading.
>> >
>> > As you can see from this output, there are 4 processors and 4 cores,
>> all on
>> > one physical id.  I think this means that there are no CPUs due to
>> > hyperthreading.  If you look at the flags, it has "ht" that I thought
>> meant
>> > hyperthreading is enabled, both in the BIOS and in the kernel.  But
>> > apparently not.
>> >
>> > Anyone know how to enable hyperthreading?
>> >
>> > [root at manzanita log]# grep -E "processor|physical id|core id|flags"
>> > /proc/cpuinfo
>> > processor       : 0
>> > physical id     : 0
>> > core id         : 0
>> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca
>> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx
>> rdtscp
>> > lm constant_tsc ida nonstop_tsc pni monitor ds_cpl vmx smx est tm2 ssse3
>> > cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm
>> > processor       : 1
>> > physical id     : 0
>> > core id         : 1
>> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca
>> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx
>> rdtscp
>> > lm constant_tsc ida nonstop_tsc pni monitor ds_cpl vmx smx est tm2 ssse3
>> > cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm
>> > processor       : 2
>> > physical id     : 0
>> > core id         : 2
>> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca
>> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx
>> rdtscp
>> > lm constant_tsc ida nonstop_tsc pni monitor ds_cpl vmx smx est tm2 ssse3
>> > cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm
>> > processor       : 3
>> > physical id     : 0
>> > core id         : 3
>> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca
>> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx
>> rdtscp
>> > lm constant_tsc ida nonstop_tsc pni monitor ds_cpl vmx smx est tm2 ssse3
>> > cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm
>> >
>> > Thanks,
>> >
>> > Michael
>> >
>> > _______________________________________________
>> > Web Page:  http://lug.boulder.co.us
>> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>> > Join us on IRC: irc.hackingsociety.org port=6667
>> channel=#hackingsociety
>> _______________________________________________
>> Web Page:  http://lug.boulder.co.us
>> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>>
>
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20121012/3bf62cc0/attachment.html>


More information about the LUG mailing list