09-04-2014
Quote:
Originally Posted by
firefox111
is anyone using versioned WPAR's?
Has anyone clustered them with PowerHA?
In any environment i came into WPAR were frowned upon and ultimately they weren't used. There is simply not enough gain in it to use them, IMHO. A WPAR is a sort-of
chroot-environment with some management extensions decorating it and it is (IMHO) by far easier to manage LPARs than to manage WPARs within an LPAR. You will have less dependencies, less restrictions and less hassle overall with LPARs, whereas the WPARs only give you a (very small) advantage in terms of necessary disk space and maybe a slightly better usage of given resources (memory, CPU) - but even this is doubtful.
I hope this helps.
bakunin
9 More Discussions You Might Find Interesting
1. Infrastructure Monitoring
Hi,
I have a shared AIX wpar configured.
I have started snmpd process on shared AIX wpar.
But when i tried to query a MIB id using the following command
/opt/OV/bin/snmpget -d -v 1 -c public -p <hostname> .1.3.6.1.2.1.1.7.0
i get the following error message
#... (0 Replies)
Discussion started by: avazeer
0 Replies
2. AIX
Hello,
We have a system running AIX 6.1.7.1. We have created a Workload Partition(wpar) on this system with wpar specific routing enabled.
On wpar, we are running DNS (UDP/53) and syslog (UDP/514).
en0: 1.1.1.1/255.255.255.0 NOT assigned to any wpar
en1:... (0 Replies)
Discussion started by: 03sep2011
0 Replies
3. AIX
seems to be WPAR is quite easy to set up..without additional licenses..
If I don't need Linux and all my legacy and new apps are happy in AIX 7.1 (the latest OS), I could save all troubles and use WPAR.
Can someone comment on this ??
One copy of OS to maintain, so to speak..
... (4 Replies)
Discussion started by: ppchu99
4 Replies
4. Shell Programming and Scripting
Hi All,
This is for WPAR monitoring shell script, earlier opened thread was closed, had to open a new thread, as suggested I have used script as below, But am trying to get the output in below format, need suggestions with it. Below is the lswpar output, required output format.
... (7 Replies)
Discussion started by: aix_admin_007
7 Replies
5. UNIX for Advanced & Expert Users
Can anyone please let know difference between LPAR/DLPAR/WPAR.
and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies
6. AIX
Hi.
I've setup a wpar on aix
mkwpar -h ibmunix2 -i -r -N interface=en0 address=10.6.0.1 netmask=255.255.255.0 -n ibmunix2
When i log into ibmunix2 it can't ping any external host,include the ibm host.
How to set route for network please?
I've set ibmunix2 with a different subnet.
... (7 Replies)
Discussion started by: Linusolaradm1
7 Replies
7. AIX
Anyone running CICS TX in a WPAR ?
In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue).
Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned... (4 Replies)
Discussion started by: The Doctor
4 Replies
8. AIX
AIX 7.1
New to WPAR, hopefully just missing something simple here.
Creating the WPAR like this.....
(The box where the WPAR is hosted does have an iscsi protocol device)
mkwpar -h wpar08 -l -n wpar08 -N interface=en0 address=xxx.xx.xx.xxx netmask=255.255.255.0 -D devname=/dev/iscsi0 -D... (0 Replies)
Discussion started by: TomR
0 Replies
9. AIX
I have this error when I'm trying to do clogin from AIX 7200-00-00-0000 into a wpar with AIX 5.2
abanksPaDesa2:/> clogin AbanksBDPA_wpar
exec: A file or directory in the path name does not exist
somebody can help me to fix this? I'm restoring the wpar from wpar mksysb not a mksysb from... (2 Replies)
Discussion started by: sandra25350
2 Replies
LEARN ABOUT FREEBSD
pthread_attr_setaffinity_np
PTHREAD_ATTR_AFFINITY_NP(3) BSD Library Functions Manual PTHREAD_ATTR_AFFINITY_NP(3)
NAME
pthread_attr_getaffinity_np, pthread_attr_setaffinity_np -- manage CPU affinity in thread attribute objects
LIBRARY
POSIX Threads Library (libpthread, -lpthread)
SYNOPSIS
#include <pthread_np.h>
int
pthread_attr_getaffinity_np(const pthread_attr_t *pattr, size_t cpusetsize, cpuset_t *cpusetp);
int
pthread_attr_setaffinity_np(pthread_attr_t *pattr, size_t cpusetsize, const cpuset_t *cpusetp);
DESCRIPTION
The pthread_attr_getaffinity_np() and pthread_attr_setaffinity_np() functions allow the manipulation of sets of CPUs available to the speci-
fied thread attribute object.
Masks of type cpuset_t are composed using the CPU_SET macros. The kernel tolerates large sets as long as all CPUs specified in the set
exist. Sets smaller than the kernel uses generate an error on calls to pthread_attr_getaffinity_np() even if the result set would fit within
the user supplied set. Calls to pthread_attr_setaffinity_np() tolerate small sets with no restrictions.
The supplied mask should have a size of cpusetsize bytes. This size is usually provided by calling sizeof(cpuset_t) which is ultimately
determined by the value of CPU_SETSIZE as defined in <sys/cpuset.h>.
pthread_attr_getaffinity_np() retrieves the mask from the thread attribute object specified by pattr, and stores it in the space provided by
cpusetp.
pthread_attr_setaffinity_np() sets the mask for the thread attribute object specified by pattr to the value in cpusetp.
RETURN VALUES
If successful, the pthread_attr_getaffinity_np() and pthread_attr_setaffinity_np() functions will return zero. Otherwise an error number
will be returned to indicate the error.
ERRORS
The pthread_attr_getaffinity_np() functions will fail if:
[EINVAL] The pattr or the attribute specified by it is NULL.
[ERANGE] The cpusetsize is too small.
The pthread_attr_setaffinity_np() function will fail if:
[EINVAL] The pattr or the attribute specified by it is NULL.
[EINVAL] The cpusetp specified a CPU that was outside the set supported by the kernel.
[ERANGE] The cpusetsize is too small.
[ENOMEM] Insufficient memory exists to store the cpuset mask.
SEE ALSO
cpuset(1), cpuset(2), cpuset_getid(2), cpuset_setid(2), pthread_get_affinity_np(3), pthread_set_affinity_np(3)
STANDARDS
The pthread_attr_getaffinity_np and pthread_attr_setaffinity_np functions are non-standard FreeBSD extensions and may be not available on
other operating systems.
HISTORY
The pthread_attr_getaffinity_np and pthread_attr_setaffinity_np functions first appeared in FreeBSD 7.2.
AUTHORS
The pthread_attr_getaffinity_np and pthread_attr_setaffinity_np functions were written by David Xu <davidxu@FreeBSD.org>, and this manpage
was written by Xin LI <delphij@FreeBSD.org>.
BSD
January 8, 2010 BSD