01-11-2012
Just guessing now, could this be caused by dynamic CPU folding?
In this case the effect would not be visible all the time and more likely
occur on LPARs with low or volatile load...
Greetings,
Greg
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there an easy way in Solaris to count the number of processors? (2 Replies)
Discussion started by: hshapiro
2 Replies
2. UNIX for Advanced & Expert Users
I gave mpstat command in my system..
the o/p is like below
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl
0 199 3 198 112 5 78 95 124 55 0 9 25 14 7 54
1 186 2 97 92 1 45 94 121 41 0 220 27 14 5 54
... (2 Replies)
Discussion started by: shahnazurs
2 Replies
3. Solaris
Hi,
I would like to clearly understand the output of the mpstat command. What is the mutex spins and also context switches? What if we saw that the number of mutex spins is high. Basically, what to look for in the output of the mpstat command? What is wrong and what is ok. what is the value... (3 Replies)
Discussion started by: Pouchie1
3 Replies
4. UNIX for Dummies Questions & Answers
We have purchased four intels xeon processors
Intel® Xeon® Processor E7530 (12M Cache, 1.86 GHz, 5.86 GT/s Intel® QPI) with SPEC Code(s) SLBRJ
As per the specification each cpu has 6 cores therefore we have 24 cores (considering 4 cpus).
Now how would i calculate the number of vcpus that can... (1 Reply)
Discussion started by: pinga123
1 Replies
5. Red Hat
Hi,
I am observing high load average on RHEL5 server and need to check the number of core processors available on the box to give me a bigger picture on whether or not I should be worried.
I have always checked the physical count quite simply.....
# grep 'physical id' /proc/cpuinfo |... (10 Replies)
Discussion started by: Duffs22
10 Replies
6. Red Hat
Hello,
sysinfo throws out below 3 CPU counts. Can anyone help me understand what each of these means?
CPU Count Socketed is 2
CPU Count Physical is 8
CPU Count Virtual is 16
First one seems obvious. However, I wonder how there can be 8 Physical CPUs, if... (2 Replies)
Discussion started by: hnhegde
2 Replies
7. Shell Programming and Scripting
HI I ma using mpstat and sar commands to check the cpu utilisation
but the results are not matching .I dont understand why thisis happening?
$ sar -u 12 5
Linux 2.6.9-89.35.1.ELhugemem (abcd.efgh.com) 03/07/2013
02:43:16 AM CPU %user %nice %system %iowait %idle... (1 Reply)
Discussion started by: ptappeta
1 Replies
8. Shell Programming and Scripting
I have a script which runs the mpstat and prints the output in a file. In order capture highest cpu ususage from the generated output file,
have to manually tail the output file and need to grab which cpu has highest value (which is very annoying)
Is there a way we can automate that process of... (3 Replies)
Discussion started by: Optimus81
3 Replies
9. AIX
To get only the cpu info from the topas command terminal.
CPU User% Kern% Wait% Idle% Physc Entc
ALL 2.3 4.4 0.0 93.3 0.07 7.7
I tried some thing like this but did not work
topas << done
grep "ALL"
q
done
Can someone help me in this. (5 Replies)
Discussion started by: rpm120
5 Replies
10. AIX
seeing weirdness across some 7.1.5.1 LPARs - they all have 2 vCPUs allocated shared. With prtconf they show 2 CPUs, 'lsdev -c processor' concurs, and 'lsattr -El procX' shows that SMT is enabled and there are 2 SMT threads (power5, sorry). Yet running topas on them shows 2 CPUs on some and 4 on... (3 Replies)
Discussion started by: maraixadm
3 Replies
LEARN ABOUT SUNOS
atomic_inc_ptr
atomic_inc(3C) atomic_inc(3C)
NAME
atomic_inc, atomic_inc_8, atomic_inc_uchar, atomic_inc_16, atomic_inc_ushort, atomic_inc_32, atomic_inc_uint, atomic_inc_ulong,
atomic_inc_64, atomic_inc_ptr, atomic_inc_8_nv, atomic_inc_uchar_nv, atomic_inc_16_nv, atomic_inc_ushort_nv, atomic_inc_32_nv,
atomic_inc_uint_nv, atomic_inc_ulong_nv, atomic_inc_64_nv, atomic_inc_ptr_nv - atomic inrement operations
SYNOPSIS
#include <atomic.h>
void atomic_inc_8(volatile uint8_t *target);
void atomic_inc_uchar(volatile uchar_t *target);
void atomic_inc_16(volatile uint16_t *target);
void atomic_inc_ushort(volatile ushort_t *target);
void atomic_inc_32(volatile uint32_t *target);
void atomic_inc_uint(volatile uint_t *target);
void atomic_inc_ulong(volatile ulong_t *target);
void atomic_inc_64(volatile uint64_t *target);
void atomic_inc_ptr(volatile void *target);
uint8_t atomic_inc_8_nv(volatile uint8_t *target);
uchar_t atomic_inc_uchar_nv(volatile uchar_t *target);
uint16_t atomic_inc_16_nv(volatile uint16_t *target);
ushort_t atomic_inc_ushort_nv(volatile ushort_t *target);
uint32_t atomic_inc_32_nv(volatile uint32_t *target);
uint_t atomic_inc_uint_nv(volatile uint_t *target);
ulong_t atomic_inc_ulong_nv(volatile ulong_t *target);
uint64_t atomic_inc_64_nv(volatile uint64_t *target);
void *atomic_inc_ptr_nv(volatile void *target);
These functions enable the inrementing (by one) of the value stored in target to occur in an atomic manner.
The *_nv() variants of these functions return the new value of target.
No errors are defined.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Stable |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
atomic_add(3C), atomic_and(3C), atomic_bits(3C), atomic_cas(3C), atomic_dec(3C), atomic_or(3C), atomic_swap(3C), membar_ops(3C),
attributes(5), atomic_ops(9F)
The *_nv() variants are substantially more expensive on some platforms than the versions that do not return values. Do not use them unless
you need to know the new value atomically.
13 May 2005 atomic_inc(3C)