10-15-2010
Hi.
It relates to multi-threading. It means 2 cores, 4 threads. Each core can work on two tasks at the same time.
This User Gave Thanks to Scott For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi..,
my dout is a solaris server is having 16 cpu's.
in tht one cpu running some error process, accupaying more space.
I wanna down tht particular CPU only with out interrupting the other 15
CPU's. how can i do this. is there any command for this ?? (5 Replies)
Discussion started by: b.janardhanguru
5 Replies
2. UNIX for Dummies Questions & Answers
hi,
i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Discussion started by: pankajd
3 Replies
3. Solaris
Hello Friends,
On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization.
=========================================================================
$ prstat -a
... (4 Replies)
Discussion started by: mahive
4 Replies
4. Solaris
Can anyone tell me difference between cpu-shares vs cpu-cap in solaris & how FSS will work with cpu-caps ? (9 Replies)
Discussion started by: fugitive
9 Replies
5. Solaris
Hi,
I am a weblogic Admin
I our env there are 5 servers running in one Solaris 10 Sparc machine.
But when i tried for process status using <top> command
I got the following output
load averages: 1.75, 2.18, 2.12; up 134+08:28:49
22:24:21
79 processes: 77 sleeping, 1 running,... (1 Reply)
Discussion started by: Joseph Antoine
1 Replies
6. Solaris
Hi All,
What is the difference between CPU CHIP and CUP ID on SUN/ Oracle M5000 servers..
Thanks in advance (3 Replies)
Discussion started by: kumarmani
3 Replies
7. UNIX for Dummies Questions & Answers
We have a single threaded application which is restricted by CPU usage even though there are multiple CPUs on the server, hence leading to significant performance issues. Is it possible to merge / combine multiple CPUs at OS level so it appear as a single CPU for the application? (6 Replies)
Discussion started by: Dissa
6 Replies
8. AIX
Hi All,
It may be a n00b question, but i really want to know , How Entitled Capacity is less and Used CPU is more when there is no Free CPU is available in the managed system.
I have 5LPARs in a MS with Dual VIO.
Managed System CPU details
Available: 0.20
Assigned to partitions: 15.80... (11 Replies)
Discussion started by: Thala
11 Replies
9. Red Hat
Hi
i have 2 esxi. one is amd based cpu and the other is intel based cpu.
i have a redhat linux machine that was created in amd cpu esxi, now i need to migrate it (powered off) to INTEL based esxi. will the redhat machine will be OK with that?
Thanks (2 Replies)
Discussion started by: guy3145
2 Replies
10. UNIX for Beginners Questions & Answers
I read that Entitlement CPU should be set to max 75% compare to Virtual CPU. May I know the reason.
I have set the Entitlement CPU = Virtual CPU on AIX . It works fine .
Can you help to understand. (1 Reply)
Discussion started by: gabhanes
1 Replies
LEARN ABOUT X11R4
xlockdisplay
XInitThreads(3) XLIB FUNCTIONS XInitThreads(3)
NAME
XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support
SYNTAX
Status XInitThreads(void);
void XLockDisplay(Display *display);
void XUnlockDisplay(Display *display);
ARGUMENTS
display Specifies the connection to the X server.
DESCRIPTION
The XInitThreads function initializes Xlib support for concurrent threads. This function must be the first Xlib function a multi-threaded
program calls, and it must complete before any other Xlib call is made. This function returns a nonzero status if initialization was suc-
cessful; otherwise, it returns zero. On systems that do not support threads, this function always returns zero.
It is only necessary to call this function if multiple threads might use Xlib concurrently. If all calls to Xlib functions are protected
by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini-
tialization is not required. It is recommended that single-threaded programs not call this function.
The XLockDisplay function locks out all other threads from using the specified display. Other threads attempting to use the display will
block until the display is unlocked by this thread. Nested calls to XLockDisplay work correctly; the display will not actually be unlocked
until XUnlockDisplay has been called the same number of times as XLockDisplay. This function has no effect unless Xlib was successfully
initialized for threads using XInitThreads.
The XUnlockDisplay function allows other threads to use the specified display again. Any threads that have blocked on the display are
allowed to continue. Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must
be called an equal number of times before the display is actually unlocked. This function has no effect unless Xlib was successfully ini-
tialized for threads using XInitThreads.
SEE ALSO
Xlib - C Language X Interface
X Version 11 libX11 1.2.1 XInitThreads(3)