06-09-2014
A virtual processor is defined as a CPU component able to execute an independent thread so yes, 16 threads means 16 VCPUs.
This User Gave Thanks to jlliagre For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
What is the command to identify whether a processor is single core / dual core in solaris ?
Thanks. (2 Replies)
Discussion started by: RAA
2 Replies
2. Shell Programming and Scripting
I wrote a very simple script that matches combinations of alphabetic characters (1-5). I want to use it to test CPU speeds of different hardware/platforms. The problem is that on multi-core/processor systems, only one CPU is being utilized to execute the script. Is there a way to change that?... (16 Replies)
Discussion started by: ph0enix
16 Replies
3. Red Hat
Hey all,
dmidecode | grep -i CPU
Socket Designation: CPU 0
Version: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
Socket Designation: CPU 1
Version: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
cat /proc/cpuinfo | grep -i cpu
cpu family : 6... (24 Replies)
Discussion started by: rmokros
24 Replies
4. UNIX for Dummies Questions & Answers
Hi folks,
I want to know how to run two unix programs on two different cpu cores on a 2-core or 4-core or 8-core CPU machine? Extending this how would i run four and eight unix programs on 4-core and 8-core machine respectively?
If this can be done, how to know which program is assigned to... (1 Reply)
Discussion started by: kaaliakahn
1 Replies
5. Programming
Hi
on multi-core system - I know I can set each process to run on specific core (Processor Affinity).
If I want to set process (which contains several threads) to run on group of core, how can I do it ?
For example:
If we have 8 core,
and two process each process contain 4 threads.
And I... (2 Replies)
Discussion started by: laro1983
2 Replies
6. Solaris
Hello All,
How do I find the number of CPU's, virtual processors in solaris 10?
Thank you
Sunil Kumar (2 Replies)
Discussion started by: msgforsunil
2 Replies
7. Red Hat
Hi all.
I have a question about linux command to find number of CPU and Core.
I usually use the command dmidecode -t processor to find cpu and core numbers . On this machine with Red Hat 4. 0 when I try to insert the command is returned the error
-bash: dmidecode: command not found
I try to... (8 Replies)
Discussion started by: piccolinomax
8 Replies
8. Solaris
Hi,
I am trying to gather cpu core details and used this script - Solaris & Scripting: Script - Find cpu - model / type / count / core / thread / speed - Solaris Sparc
For auuditing purpose, we want to know how many cores are being used by Oracle, because oracle license will be charged on... (2 Replies)
Discussion started by: solaris_1977
2 Replies
LEARN ABOUT OSF1
sched_yield
sched_yield(3) Library Functions Manual sched_yield(3)
NAME
sched_yield - Signals scheduler a willingness to yield to another thread.
LIBRARY
DECthreads POSIX 1003.1c Library (libpthread.so)
SYNOPSIS
#include <pthread.h>
void sched_yield(void);
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
IEEE Std 1003.1c-1995, POSIX System Application Program Interface
PARAMETERS
None
DESCRIPTION
This routine forces the running thread to relinquish the processor until it again becomes the head of its thread list. This routine noti-
fies the thread scheduler that the current thread is willing to release its processor to other threads of equivalent or greater scheduling
precedence. (A thread generally will release its processor to a thread of a greater scheduling precedence without calling this routine.)
If no other threads of equivalent or greater scheduling precedence are ready to execute, the thread continues.
This routine can allow knowledge of the details of an application to be used to improve its performance. If a thread does not call
sched_yield, other threads may be given the opportunity to run at arbitrary points (possibly even when the interrupted thread holds a
required resource). By making strategic calls to sched_yield, other threads can be given the opportunity to run when the resources are
free. This can sometimes improve performance by reducing contention for the resource.
As a general guideline, consider calling this routine after a thread has released a resource (such as a mutex) that is heavily contended
for by other threads. This can be especially important if the program is running on a uniprocessor machine, or if the thread acquires and
releases the resource inside a tight loop.
Use this routine carefully and sparingly, because misuse can cause unnecessary context switching which will increase overhead and degrade
performance. For example, it is counter-productive for a thread to yield while it holds a resource that the threads to which it is yielding
will need. Likewise, it is pointless to yield unless there is likely to be another thread that is ready to run.
RETURN VALUES
None
RELATED INFORMATION
Functions: pthread_attr_setschedparam(3), pthread_setschedparam(3)
Manuals: Guide to DECthreads and Programmer's Guide
delim off
sched_yield(3)