Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not sure what you mean by "fullist potential" but if you want to see if both are detected then use cat /proc/cpuinfo or top then hit the 1 key and it will show both processors and the load on each.
Not sure whether you should use the SMP core for that, since it's not 2 physical cores, but see what FC has detected by running cat /proc/cpuinfo or cpufreq-info
If you see 2 CPU's then your dual core CPU is enabled.
Not sure whether you should use the SMP core for that, since it's not 2 physical cores, but see what FC has detected by running cat /proc/cpuinfo or cpufreq-info
If you see 2 CPU's then your dual core CPU is enabled.
That is wrong. A dual core processor is the same as 2 one core processor system. The kernel have to be compiled for SMP or the other processor will just idle. If you are thinking of Hyperthreading, then yes it is not two phyiscal processors.
If your running DC programs, they usually have a flag that you can set for each core (through the means of a "Machine ID"/"Affinity")
But usually the OS decides by itself how to spread tasks over the cores evenly.
This is what I got. Guess this means it is working well. I am runnig a smp kernel.
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2300 @ 1.66GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr
bogomips : 3330.56
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2300 @ 1.66GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr
bogomips : 3325.22
just an idea is there anyway to set affinity per program?
No need to set affinity if the program is multi-threaded it will use both processors although a quick search here on Debian reveals schedutils which seems to be what you would want for it.
Code:
>$ apt-cache search show schedutils
Package: schedutils
Priority: optional
Section: utils
Installed-Size: 84
Maintainer: Guus Sliepen <guus@debian.org>
Architecture: amd64
Version: 1.4.0-1
Depends: libc6 (>= 2.3.5-1)
Filename: pool/main/s/schedutils/schedutils_1.4.0-1_amd64.deb
Size: 16484
MD5sum: 59eecf7462463f322cc9237e2828a689
SHA1: 3c413ffbd8cdeaf3338f218813c2bb81bbb4a2d0
SHA256: 9063067e02db5aa2215e5ddef2fc79738e83831d119b5e4a7ad72883cfe672fd
Description: Linux scheduler utilities
These are the Linux scheduler utilities - schedutils for short. These programs
take advantage of the scheduler family of syscalls that Linux implements across
various kernels. These system calls implement interfaces for scheduler-related
parameters such as CPU affinity and real-time attributes. The standard UNIX
utilities do not provide support for these interfaces -- thus this package.
.
The programs that are included in this package are taskset and chrt. Together
with nice and renice (not included), they allow full control of process
scheduling parameters. Suggestions for related utilities are welcome, although
it is believed (barring new interfaces) that all scheduling interfaces are
covered.
Tag: admin::kernel, interface::commandline, role::sw:utility, works-with::software:running
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.