Thread replies: 20
Thread images: 4
Thread images: 4
File: Screenshot_2016-06-20_15-04-25.png (47KB, 772x308px) Image search:
[Google]
47KB, 772x308px
Is it just me or are Core2 processors infact 2 processors on 1 chip? Because lscpu registers it as 2 CPU's, and if I disable SMP I only see "1" core.
From Linux config:
>CONFIG_SMP
>This enables support for systems with more than one CPU. If you have a system with only one CPU say N. If you have a system with more than one CPU, say Y.
>If you say N here, the kernel will run on single and multiprocessor systems, but will use only one CPU of a multiprocessor system. If you say Y here, the kernel will run on many, but not all, singleprocessor system. On a singleprocessor system, the kernel will run faster if you say N here.
>See also the Documentation/smp.tex, Documentation/smp.txt, and the SMP-HOWTO available at http://www.tldp.org/docs.html#howto.
>If you don't know what to do here, say N.
What do you think? Can I see your lscpu or /proc/cpuinfo?
>>
>>55172510
Every multicore CPU is going to do that.
>>
a core is a CPU retard
>>
>>55172510
how do you not know this?
>>
>>55172592
>>55172568
>>55172539
Isn't it 1 CPU 2 cores? Not 2 CPUs 1 core each.
>>
>>55172619
To the OS, a core and a CPU are the same. Whether it's on a separate die or in a separate socket is irrelevant. If it has separate decode units, pipelines, ALUs, etc., it's a separate processor.
>>
>>55172652
How does a OS see multi threaded cores? Is it also considered a separate cpu?
>>
>>55172671
Hyperthreaded cores will also show up as multiple processors. An OS that's aware of hyperthreading can tell that they're connected and schedule smarter. An OS that isn't will just see them as separate CPUs and schedule tasks to them as such, which will get some benefit from the hyperthreading but not as much as an OS that knows how to use it properly will.
>>
>>55172671
Yes, that's the idea of things like hyperthreading.
>>
>>55172671
Don't know about Windows, but on Linux /proc/cpuinfo lists each core like it was a separate CPU.
>>
>>55172699
Thanks for the info!
>>
File: Capture.png (8KB, 300x167px) Image search:
[Google]
8KB, 300x167px
>>55172715
Yes.
This is a single hyperthreaded quad core i7 4700MQ.
>>
File: Capture.png (18KB, 403x379px) Image search:
[Google]
18KB, 403x379px
>>55172762
And in Task Manager...
>>
>>55172762
FAKE MOAR CORES
>>
>>55173492
Those are threads too
>>
>>55174387
"thread" literally means "faka cores"
>>
>>55172510
The Intel Core 2 Solo has one processor core; the Core 2 Duo has two; the Core 2 Quad has four.
>>
>>55174833
>>55173492
Uhh, no. A thread is a thread of execution with a shared stack with the parent thread and all other threads that this parent has created.
Threads may run simultaneously on multiple cores, and on Intel processors with hyperthreading it just means that for every cache, core frontend etc. there are two logical execution cores.
They are not fake cores. They are physical, true CPU cores. It's just that they share the execution resources, and thus are not a full CPU of their own. This is faster than being limited to 4 cores, but a true 8-core CPU would beat the shit out of 4-core SMT CPU.
>>
>>55174833
You're retarded
>>
File: 1418955862001.jpg (12KB, 300x400px) Image search:
[Google]
12KB, 300x400px
>>55172510
Jesus christ /g/
Thread posts: 20
Thread images: 4
Thread images: 4