Sponsored Content
Full Discussion: SMP support in Linux 7.3
Top Forums UNIX for Dummies Questions & Answers SMP support in Linux 7.3 Post 27569 by LivinFree on Tuesday 3rd of September 2002 09:50:28 PM
Old 09-03-2002
I don't understand your question...
I would assume that it's just like any other OS that uses SMP for a single instance of the operating system (or other dedicated software)...
 

7 More Discussions You Might Find Interesting

1. SCO

SCO unix 5.0.7 (SMP)

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

Unix/Linux Support?

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

Dual Intel Xeon 2.4Ghz - Linux 2.4.26 SMP

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

full shutdown in smp

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

socket close() -w- pthreads linux 2.6.18.2-34 (suse) SMP

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

MPI + Cluster SMP

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

Profiling results and SMP

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
SMP(4)							   BSD Kernel Interfaces Manual 						    SMP(4)

NAME
SMP -- description of the FreeBSD Symmetric Multi-Processor kernel SYNOPSIS
options SMP DESCRIPTION
The SMP kernel implements symmetric multi-processor support. COMPATIBILITY
Support for multi-processor systems is present for all Tier-1 architectures on FreeBSD. Currently, this includes amd64, i386, ia64, and sparc64. Support is enabled using options SMP. It is permissible to use the SMP kernel configuration on non-SMP equipped motherboards. I386 NOTES For i386 systems, the SMP kernel supports motherboards that follow the Intel MP specification, version 1.4. In addition to options SMP, i386 also requires device apic. The mptable(1) command may be used to view the status of multi-processor support. The number of CPUs detected by the system is available in the read-only sysctl variable hw.ncpu. FreeBSD allows specific CPUs on a multi-processor system to be disabled. The sysctl variable machdep.hlt_cpus is an integer bitmask denoting CPUs to halt, counting from 0. Setting a bit to 1 will result in the corresponding CPU being disabled. The sched_ule(4) scheduler implements CPU topology detection and adjusts the scheduling algorithms to make better use of modern multi-core CPUs. The sysctl variable kern.sched.topology_spec reflects the detected CPU hardware in a parsable XML format. The top level XML tag is <groups>, which encloses one or more <group> tags containing data about individual CPU groups. A CPU group contains CPUs that are detected to be "close" together, usually by being cores in a single multi-core processor. Attributes available in a <group> tag are "level", corre- sponding to the nesting level of the CPU group and "cache-level", corresponding to the level of CPU caches shared by the CPUs in the group. The <group> tag contains the <cpu> and <flags> tags. The <cpu> tag describes CPUs in the group. Its attributes are "count", corresponding to the number of CPUs in the group and "mask", corresponding to the integer binary mask in which each bit position set to 1 signifies a CPU belonging to the group. The contents (CDATA) of the <cpu> tag is the comma-delimited list of CPU indexes (derived from the "mask" attribute). The <flags> tag contains special tags (if any) describing the relation of the CPUs in the group. The possible flags are cur- rently "HTT" and "SMT", corresponding to the various implementations of hardware multithreading. An example topology_spec output for a sys- tem consisting of two quad-core processors is: <groups> <group level="1" cache-level="0"> <cpu count="8" mask="0xff">0, 1, 2, 3, 4, 5, 6, 7</cpu> <flags></flags> <children> <group level="2" cache-level="0"> <cpu count="4" mask="0xf">0, 1, 2, 3</cpu> <flags></flags> </group> <group level="2" cache-level="0"> <cpu count="4" mask="0xf0">4, 5, 6, 7</cpu> <flags></flags> </group> </children> </group> </groups> This information is used internally by the kernel to schedule related tasks on CPUs that are closely grouped together. FreeBSD supports hyperthreading on Intel CPU's on the i386 and AMD64 platforms. Since using logical CPUs can cause performance penalties under certain loads, the logical CPUs can be disabled by setting the machdep.hlt_logical_cpus sysctl to one. Note that this operation is different from the mechanism used by the cpuset(1). SEE ALSO
mptable(1), sysctl(8), condvar(9), msleep(9), mtx_pool(9), mutex(9), sema(9), sx(9), rwlock(9), sched_4bsd(4), sched_ule(4), cpuset(1) HISTORY
The SMP kernel's early history is not (properly) recorded. It was developed in a separate CVS branch until April 26, 1997, at which point it was merged into 3.0-current. By this date 3.0-current had already been merged with Lite2 kernel code. FreeBSD 5.0 introduced support for a host of new synchronization primitives, and a move towards fine-grained kernel locking rather than reliance on a Giant kernel lock. The SMPng Project relied heavily on the support of BSDi, who provided reference source code from the fine- grained SMP implementation found in BSD/OS. FreeBSD 5.0 also introduced support for SMP on the ia64 and sparc64 architectures. AUTHORS
Steve Passe <fsmp@FreeBSD.org> BSD
May 7, 2008 BSD
All times are GMT -4. The time now is 03:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy