Sponsored Content
Full Discussion: LPAR
Operating Systems AIX LPAR Post 302377956 by pchangba on Sunday 6th of December 2009 03:35:00 AM
Old 12-06-2009
i am not able to find the difference of CORE and WAY.
As my P6 550 specs says it is
2-core 4.2 GHz POWER6 Processor Card qty=2
Can you clarify
 

10 More Discussions You Might Find Interesting

1. AIX

LPAR and CFGMGR

I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf.... (1 Reply)
Discussion started by: LegendMan
1 Replies

2. AIX

Autostart of LPAR

Hi, I have 2 lpars on my AIX that needs to be started manually after each reboot. Because the servers are storing the NFS and NIS info, other servers won't run correctly until they start up. I found in IBM documentation the steps to make it automatic. My question is, I want to know if... (2 Replies)
Discussion started by: rahzzbietel
2 Replies

3. AIX

ldom and lpar

hi, Plz let me know if the concept of sun ldom and aix lpar is same or not. thnx, snj (1 Reply)
Discussion started by: snjksh
1 Replies

4. AIX

LPAR creation

can i get a step b syep explanation in creating LPAR... i have searched for tutorials i couldn't find the right one.... (2 Replies)
Discussion started by: udtyuvaraj
2 Replies

5. AIX

Bootting up a new LPAR

I have created a new LPAR using IVM. I activated the LPAR, and start the window terminal (java), it prompt me for the padmin password. After keyin the password, it will shows BOOTP parameter. I am just wondering how come it didnt go to screen where i can select to go into SMS menu to pick... (0 Replies)
Discussion started by: wingcross
0 Replies

6. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

7. AIX

Mirroring in LPAR

Hi Folks, I am a newbie in AIX. Can someone please tell me how to do root mirroring in AIX LPAR which is created from mksysb image via HMC/NIM. ? AIX 5.3/6.1 Let me know. Thanks in advance (2 Replies)
Discussion started by: snchaudhari2
2 Replies

8. AIX

Hostname for each lpar

Hi Gurus, Can a AIX server with 4 LPARs, each having it's own hostname on the same physical host. Is this possible? Thanks, S (2 Replies)
Discussion started by: svajhala
2 Replies

9. AIX

Lpar migration

We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2 Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies

10. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies
pset_getattr(2) 						System Calls Manual						   pset_getattr(2)

NAME
pset_getattr(), pset_setattr() - manage processor set attributes SYNOPSIS
DESCRIPTION
The function returns the current value of the attribute type for the processor set pset in the memory location pointed to by val. The function assigns the value val to the attribute type for processor set pset. A user can not change the attribute values for the system default processor set using the function. A user with the privilege or a user with READ permission for the processor set may query any attribute values. The following processor set attributes may be queried or changed through these functions: The GID (group id) of the processor set owner. The creator's GID is assigned at processor set creation time. A user with the privilege or the pset owner may change the value of this attribute. The UID of the processor set owner. The creator is assigned as the owner at processor set creation time. A user with the privilege or the pset owner may change the value of this attribute. The access permission bitmask for the processor set. These are defined similar to file access permissions. There are three types of access: The user can bind its process or thread to the processor set using the function (see pset_bind(2)). The user can query the processor set attributes. The user can modify the processor set attributes and configuration, and destroy the processor set. The following bit values are used for the access bitmask: All users in processor set owner's group have EXEC access. All users in processor set owner's group have READ access. All users in processor set owner's group have WRITE access. All others have EXEC access. All others have READ access. All others have WRITE access. The processor set owner has EXEC access. The processor set owner has READ access. The processor set owner has WRITE access. A newly created processor set by default has READ and EXEC access for everyone, but WRITE access only for the processor set owner. A user with the privilege or the pset owner may change the value of the attribute. A value of indicates that processors in this processor set are configured to receive external interrupts. It may be assigned a value of to disable all processors in the processor set from receiving and processing external I/O interrupts. Not all platforms may support this feature. By default, I/O interrupts are enabled on all processors. The feature may be useful for some realtime applica- tions where unpredictable interrupt handling overhead may adversely impact the application's response time requirements. Only a user with the privilege may change this attribute. Indicates the behavior when a request to destroy a non-empty processor set is made through the function. Possible values are: Reassign all processors in the processor set pset to the system default processor set. Migrate all threads and processes bound to this processor set to the system default processor set. This is the default value for this attribute. Make the request fail with an error if there are threads or processes bound to the processor set or if there are processors assigned to the processor set. Make the request fail with an error if there are active threads or processes bound to the processor set. Otherwise, perform the operation by reas- signing the processors in the pset to the system default processor set. A user with the privilege or a user with WRITE permissions may change the value of this attribute. Indicates the behavior when a request to bind a process or a thread to an empty processor set is made through the function. Possible values are: Go through with the request. However, the affected threads will not be scheduled to execute until a processor is assigned to the empty processor set. Reject the request with an error. This is the default value for this attribute. A user with the privilege or a user with WRITE permissions may change the value of this attribute. Indicates the behavior when a request to remove the last processor from a processor set is made through the function, or through the processor deallocation functionality. Possible values are: Make the request fail if there are active threads and processes assigned to the processor set. Assign the processor to the specified processor set, and migrate all threads and processes to the system default processor set This is the default value for this attribute. A user with the privilege or a user with WRITE permissions may change the value of the attribute. The LCPU attribute of a processor set indicates whether the physical processor cores in a pset are enabled with logical processors (LCPUs). On systems with the Hyper-Threading (HT) feature enabled, each proces- sor core may have more than one hyper-thread per physical processor core. Each hyper-thread is represented to the operating system and applications as a logical processor (LCPU). The can be set for the default processor set using the command. This attribute is supported only on system with the Hyper-Threading feature. If this feature is disabled at the firmware level or is not supported, this attribute cannot change. Enable the LCPUs in a processor set. This is the default value for systems with the Hyper-Threading feature enabled. Disable the LCPUs in the processor set. This is the default value for the systems without the Hyper-Threading feature or systems with the Hyper-Threading disabled in the firmware. The default value for any attribute can be assigned using the value in the function. Security Restrictions Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
The functions return zero on successful completion. Otherwise, -1 is returned and errno is set to indicate the error. ERRORS
or fails if one or more of the following is true: The memory location pointed to by val is not writable by the user for The specified processor set pset, the attribute type, or the attribute val is invalid. The memory location pointed to by val is NULL for The processor set functionality is not supported by the underlying HP-UX version. The requested attribute value is not supported for the function. The user does not have the necessary permissions to query or change the processor set attributes. AUTHOR
and were developed by HP. SEE ALSO
kctune(1M), psrset(1M), pset_assign(2), pset_bind(2), pset_create(2), pset_ctl(2), pset_destroy(2), privgrp(4), lcpu_attr(5), privi- leges(5). pset_getattr(2)
All times are GMT -4. The time now is 08:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy