11-14-2003
Hi,
Have you installed multi-processor license ? After that, you need a patch so xeon's can be recognized... If you have the license, tal to SCO to get the patch.
You can use mpsar to check the SMP activity.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies
2. UNIX for Dummies Questions & Answers
What is the SMP support like when you are running Linux 7.3 on a system with 2-4 CPUs? (3 Replies)
Discussion started by: AngryRabbi
3 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. Filesystems, Disks and Memory
Hello Moto
I hope someone can help
We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers..
a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Discussion started by: haggo
2 Replies
5. 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
6. 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
7. SCO
Hi
I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7.
I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies
8. 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
9. 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
10. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies
LEARN ABOUT OSF1
processor_sets
processor_sets(4) Kernel Interfaces Manual processor_sets(4)
NAME
processor_sets - Collections of processors
DESCRIPTION
A processor set is a collection of processors. When a processor set is first created, it does not contain any processors. You can add
processors to a processor set, remove processors from a processor set, and also destroy the processor set. In addition, you can assign
specific processes to a processor set.
When the system is booted, all its processors are assigned to the default processor set. Each processor in a system can be a member of
only one processor set at one time.
In addition, when you create a process, it is assigned to a processor set. Unless you indicate a specific processor set, a process is
assigned to the default processor set. A process can execute only on an processor that is included in the processor set to which the
process is assigned. If you assign a process to an empty processor set, it will not execute until a processor is assigned to the processor
set or until the process is assigned to another processor set.
Use the pset_create command or the create_pset function to create a processor set. When you first create a processor set, it does not con-
tain any processors.
Use the pset_assign_cpu command or the assign_cpu_to_pset function to assign processors to a specific processor set. When you assign a
processor to a specific processor set, the processor is removed from its current processor set.
Use the pset_destroy command or the destroy_pset function to destroy a processor set. Processors that belong to a destroyed processor set
are assigned to the default processor set.
Use the pset_assign_pid command or the assign_pid_to_pset function to assign a process to a specific processor set. In addition, you can
request that a process has exclusive access to a processor set. If a process has exclusive access to a processor set, no other process is
able to use that processor set. If a process has exclusive access to a processor set, that access will be cleared automatically when the
process exits. Note that if a process is already assigned to a processor set, a request for exclusive access to that processor set will be
denied.
Use the pset_info command to display the status of each processor set on the system as well as the status of each processor.
You must be root to create and destroy processor sets and to assign a processor to a processor set. Processor set creation and destruction
and processor assignments to processor sets are logged in the /var/adm/wtmp file.
FILES
/var/adm/wtmp
RELATED INFORMATION
Commands: pset_create(1), pset_destroy(1), pset_info(1), pset_assign_pid(1), pset_assign_cpu(1), runon(1), psrinfo(1), psradm(8)
Functions: assign_pid_to_pset(3), assign_cpu_to_pset(3), create_pset(3), destroy_pset(3) delim off
processor_sets(4)