09-04-2002
It should run just fine on a 2-4 CPU box.
According to the HOW-TO (you should really learn how to use google...), the 2.2 series kernels should theoretically work for up to 16 CPUs on an Intel machine. Redhat 7.3 uses a kernel in the 2.4 tree, so I can't be 100% sure of any changes.
Here is the HOW-TO I am referring to:
http://www.tldp.org/HOWTO/SMP-HOWTO.html
7 More Discussions You Might Find Interesting
1. SCO
I have a dell machine Dell 2600 PowerEdge it has two processor (intel Xeon ).
Is there a path or a software that will work with SCO unix in order to enable second processor and how would i know that the second processor is active.
Thanks a lot guys . (1 Reply)
Discussion started by: josramon
1 Replies
2. UNIX for Dummies Questions & Answers
If the strength of Unix based operating systems such as Linux and Red Hat are based on the fact that they are open-source. Who will provide support for personal computers or average users that uses these operating systems. Wouldn't the absence of some structured and formal support system inhibit... (8 Replies)
Discussion started by: wmosley2
8 Replies
3. Linux Benchmarks
System:
CPU/Speed: Dual Intel Xeon 2.4Ghz
Ram: 2 GB DDR 266 SDRAM
Motherboard: SuperMicro X5DE8-GG
Bus: 533MHz/400MHz system bus -
Cache: 512KB
HD Controller: EIDE Serverworks™ GC-SL Chipset
Extra GCC compiler flags:
-s... (3 Replies)
Discussion started by: Neo
3 Replies
4. Red Hat
I have installed redhat linux 9.0 on P4 HT machine. The grub boot loader shows path to smp mode and normal mode. when machine shut downs from smp version kernal , need to press the power button to power off. But in normal mode the system shut downs or power downs automatically(ie, full... (2 Replies)
Discussion started by: pcsaji
2 Replies
5. Programming
Interesting issue. There was some discussion on the LKML last year regarding the potential problems in concurrent applications reusing file descriptors in various scenarios. The main issue is that the reuse of a file descriptor and reception of data in a threaded application can be confused pretty... (1 Reply)
Discussion started by: ramen_noodle
1 Replies
6. High Performance Computing
Hola, he instalado mpich2 vs. 1.2.1p1 en un cluster de biprocesadores con las opciones por defecto (antes usaba ssm pero visto que se quedaba colgado, lo he dejado con nemesis).
El caso es que quisiera que cada vez que lanzo un job (por ejemplo de 2 procesos), cada proceso del trabajo se fuera... (1 Reply)
Discussion started by: Sonia_
1 Replies
7. Programming
The SCO OSR 5.7 system was migrated from older HP DL360 to new DL380 G7. The SMP feature was not activated on older box, it is activated now on this 4 core Xeon.
A s/w we maintain has been copied without any change over to the new box. I noticed that the application profiling does not show any... (4 Replies)
Discussion started by: migurus
4 Replies
CPUID(4) Linux Programmer's Manual CPUID(4)
NAME
cpuid - x86 CPUID access device
DESCRIPTION
CPUID provides an interface for querying information about the x86 CPU.
This device is accessed by lseek (2) or pread (2) to the appropriate CPUID level and reading in chunks of 16 bytes. A larger read size
means multiple reads of consecutive levels.
The lower 32 bits of the file position is used as the incoming %eax, and the upper 32 bits of the file position as the incoming %ecx, the
latter intended for "counting" eax levels like eax=4.
This driver uses /dev/cpu/CPUNUM/cpuid, where CPUNUM is the minor number, and on an SMP box will direct the access to CPU CPUNUM as listed
in /proc/cpuinfo.
This file is protected so that it can only be read by the user root, or members of the group root.
NOTES
The CPUID instruction can be directly executed by a program using inline assembler. However this device allows convenient access to all
CPUs without changing process affinity.
Most of the information in cpuid is reported by the kernel in cooked form either in /proc/cpuinfo or through subdirectories in
/sys/devices/system/cpu. Direct CPUID access through this device should only be used in exceptional cases.
The cpuid driver is not auto-loaded. On modular kernels you might need to use the following command to load it explicitly before use:
$ modprobe cpuid
There is no support for CPUID functions that require additional input registers.
Very old x86 CPUs don't support CPUID.
SEE ALSO
Intel Corporation, Intel 64 and IA-32 Architectures Software Developer's Manual Volume 2A: Instruction Set Reference, A-M, 3-180 CPUID ref-
erence.
Intel Corporation, Intel Processor Identification and the CPUID Instruction, Application note 485.
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2009-03-31 CPUID(4)