Sponsored Content
Operating Systems AIX Processsing Units and Virtual Processors. Post 302553149 by manoj.solaris on Wednesday 7th of September 2011 12:19:38 AM
Old 09-07-2011
Question Processsing Units and Virtual Processors.

Hi,

on redhat linux 5.5 (IBM PPC) os, whenever I am running the command top, it is showing 8 cpu.


Processing Units


Property Current Pending
Minimum 0.1
Assigned 0.8
Maximum 1
Virtual Processors


Property Current Pending
Minimum 1
Assigned 4
Maximum 4


would little bit confused between processing units and virtual processor.

I would like to see just single cpu
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX p5 virtual processors setting

Have a p570 LPAR capped/smt set to 4 physical processors. And currently have virtual processors set to 6 which gives 12 logical processors at AIX. This is for an Oracle9i database server running 4 instances. What should virtual processors be set to? at least initially? And how to determine when... (3 Replies)
Discussion started by: guttew
3 Replies

2. UNIX for Dummies Questions & Answers

UNIX File Processsing...Urgent Please

Gurus, I am faced with a situation where a source system FTPs files to a directory in UNIX and we invoke SQLLDR process to process the files..The problem is we are continoulsy (3 minute)receiving files and we are processing data every 5 minutes.. Is there a way to avoid processing files that are... (5 Replies)
Discussion started by: vr23
5 Replies

3. Hardware

Units in server racks

What does the term units mean in the context of server racks, for instance 4U? It is an indication of height, so does that mean the amount of disks the rack can hold or can the rack hold multiple motherboards / processors? (8 Replies)
Discussion started by: figaro
8 Replies

4. AIX

Need help understand Virtual Processors

First of all I have performed a Google search and internal search and found several descriptions but nothing I can wrap my head around and feel 100% confident about. I feel really silly for asking this as I manage a P6 570 with 12 lpars but I have difficulity with Virtual Processors. I can... (3 Replies)
Discussion started by: juredd1
3 Replies

5. Solaris

Strange power supply units alarms!!!

Hi folks, I encountered this alarms on a solaris server: 04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 0 is faulty 04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 1 is faulty 04/21/12 23:18:26 MNP-PGW-A_bge3 mnp 231822 Power Supply Unit 0 is faulty:CLEAR... (0 Replies)
Discussion started by: kimurayuki
0 Replies

6. UNIX and Linux Applications

Gnuplot Same Data Two Axes Different Units)

I'm pretty familiar with Gnuplot, but I've never actually come across a reasonable solution to this problem and I'm hoping someone can help me out! I think it's because I don't know how to pose the problem neatly, so please bare with me. Also new to the forum....so yeah... I have one data set (x... (3 Replies)
Discussion started by: TC69
3 Replies

7. Solaris

How to count number of physical and virtual processors on Solaris machine.?

hi, I am using command psrinfo -p to check the number of physical processors present on any soalris machine.I want to check the number of virtual processors assigned for particular solaris machine. which command/set of command need to be used which can grep or show the total virtual processors... (8 Replies)
Discussion started by: omkar.jadhav
8 Replies

8. Red Hat

Number of physical and virtual processors

Hi, i am trying to find out hpw many virtual and physical processors does any linux machine has: output of /proc/cpuinfo is as below : # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU... (8 Replies)
Discussion started by: omkar.jadhav
8 Replies
sys_attrs_ipc(5)						File Formats Manual						  sys_attrs_ipc(5)

NAME
sys_attrs_ipc - attributes for the ipc kernel subsystem DESCRIPTION
This reference page describes attributes for the Interprocess Communication (ipc) kernel subsystem. In the following list, attributes whose names are preceded by an asterisk (*) can be modified at run time as well as at boot time. See sys_attrs(5) for an introduction to system attributes and how to set them. The maximum number of kernel IPC ports that can be used on the system at one time. Default value: (task-max * 3 + thread_max) + (thread_max * 2) + 2000 (Values of variables used to establish default value: task_max = nproc +1; thread_max = nproc *2; nproc = 20 + 8 * maxusers) Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. Maximum size, in bytes, of a single System V message. Default value: 8192 (bytes, which equal 1 page) Minimum value: 0 Maximum value: INT_MAX Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging system. Maximum number of bytes that can be queued to a single System V message queue. Default value: 16,384 (bytes, which equal 2 pages) Minimum value: 0 Maximum value: INT_MAX Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging system. Maximum number of System V message queues that can be used on the system at one time. Default value: 50 (queues) The system rounds the number to the value associated with the next higher power of two; for example, 64. Minimum value: 0 Maximum value: INT_MAX Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging system. Maximum number of messages (system wide) that can be queued to System V message queues at one time. Default value: 40 (messages) Minimum value: 0 Maximum value: INT_MAX Values for this attribute are restricted by the amount of main memory on the system. The minimum value (0) disables the messaging system. A value that controls the maximum adjustment that can be made to any System V semaphore when a process exits. Default value: 16,384 Minimum value: 0 Maximum value: 65,536 Maximum number of System V semaphores that can be used on the system at one time. Default value: 10 (semaphores) (The system rounds the number to the value associated with the next higher power of two; for exam- ple, 16.) Minimum value: 0 Maximum value: INT_MAX Maximum number of System V semaphores that can be used by a single process at one time. Default value: 25 (semaphores) Minimum value: 0 Maximum value: INT_MAX Maximum number of operations that can be outstanding on a single System V semaphore at one time. Default value: 10 (operations) Minimum value: 0 Maximum value: INT_MAX Maximum number of undo operations that can be outstanding on a single System V semaphore at one time. Default value: 10 (operations) Minimum value: 0 Maximum value: INT_MAX Maximum integer value that any System V semaphore can contain. Default value: 32,767 Minimum value: 0 Maximum value: INT_MAX, but do not enter values higher than 65535 A value that sets default policy for shared memory allocation on NUMA-enabled systems (GS80, GS160, GS320). A value of 1 means that shared memory is striped across Resource Affinity Domains (RADs). A value of 0 means that shared memory is not striped across RADs. Default value: 1, for NUMA-enabled systems; 0 for other systems. Although you can change the value of this attribute while the system is running, there are currently no known situations for which the shm_allocate_striped value should be changed. A value of 1 is the recommended default policy for all applications on NUMA- enabled systems. Furthermore, changing the value to 0 on these systems does not override use of striped memory allocation by appli- cations that explicitly specify and control it through NUMA-specific programming interfaces. Changing the value to 1 on systems that do not support NUMA has no effect. See numa_intro(3) for an introduction to NUMA. Disables (0) or enables (1) the dumping of shared memory regions to the core file. The attribute is only used in conjunction with shared memory. Default value: 1 (on). Maximum size, in bytes, of a single System V shared memory region. Default value: 4,194,304 (bytes) (This value equals 512 pages) Minimum size, in bytes, of a single System V shared memory region. Default value: 1 (All requests are rounded to the next page size.) Maximum number of shared memory regions that can be used on the system at one time. Default value: 100 (regions) (The system rounds the number to the value associated with the next higher power of two; for example, 128.) Maximum number of System V shared memory regions that can be attached to a single process at one time. Default value: 32 (regions) If enabled (1), writes segmented shared memory contents when an application issues a core dump. If disabled (0), segmented shared memory is not written to the core dump. Default value: 1 (enabled) Because segmented shared memory can be large, the amount of time needed to dump the region to a core file and the amount of file system space required by the operation can be extensive, especially in large database environments. Therefore, although shared mem- ory can be useful for debugging, you may not want to include it in core files because of time and resource limitations. This attribute can be modified at run time. The minimum size, in bytes, of a System V shared region for the use of shared page tables. Setting this value to 0 disables the use of shared page tables for shared memory. The size must be at least equal to the value of SSM_SIZE, which is defined in the machine/pmap.h file (the default is 8 MB). This attribute can be modified at run time. Default value: SSM_SIZE Minimum value: SSM_SIZE SEE ALSO
sys_attrs(5) System Configuration and Tuning sys_attrs_ipc(5)
All times are GMT -4. The time now is 10:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy