Pinnable_frames value Post: 302800715

Sponsored Content

Operating Systems AIX Pinnable_frames value Post 302800715 by -=XrAy=- on Tuesday 30th of April 2013 10:57:05 AM

04-30-2013

Registered User

Hi,

i'm not sure what you mean exactly...

Code:

# vmo -L pinnable_frames
NAME                      CUR    DEF    BOOT   MIN    MAX    UNIT           TYPE
     DEPENDENCIES
--------------------------------------------------------------------------------
pinnable_frames           592370        592370               4KB pages         S
--------------------------------------------------------------------------------

where S = Static (If the parameter can never be changed)

regards

PS
Maybe this helps:

Code:

# vmo -h maxpin%
Help for tunable maxpin%:
Purpose:
Specifies the maximum percentage of real memory that can be pinned.
Values:
        Default: 90
        Range: 1 - 100
        Type: Dynamic
        Unit: % memory
Tuning:
Change if cannot pin memory, although free memory is available. If this value is changed, the new value should ensure that at least 4 MB of real memory will be left unpinned for use by the kernel. The vmo command converts maxpin% to the corresponding maxpin absolute value, which is the value used by the kernel. Change this parameter only in extreme situations, such as maximum-load benchmarking.
This Dynamic parameter will have its nextboot value written into the boot image if a bosboot command is issued.

-=XrAy=-

View Public Profile for -=XrAy=-

Find all posts by -=XrAy=-

LEARN ABOUT HPUX

max_mem_window

max_mem_window(5)						File Formats Manual						 max_mem_window(5)

NAME

       max_mem_window - maximum number of group-private 32-bit shared memory configurable by users

VALUES

   Default
   Allowed values
DESCRIPTION

       Processes  in  a  PA-RISC 32-bit architecture usually share the global quadrants 3 and 4 for such things as I/O mappings, shared libraries,
       shared mapped files, and so on.	However, you may wish to use quadrant 3 in a more limited sharing fashion with only a select group of pro-
       cesses.	Memory windows allow this functionality.

       If  this tunable is set to 32-bit programs always use the global Q3 and Q4 for shared memory.  If this tunable is greater than processes in
       defined groups use a Q3 private to that group, and then the globally shared Q4 if Q3 is full.

   Who is Expected to Change This Tunable?
       Anyone.

   Restrictions on Changing
       Changes to this tunable take effect immediately.

   When Should the Value of This Tunable Be Raised?
       This tunable should be raised if more group-private Q3 areas are needed by the users of the system.  Each memory window in active use  will
       require approximately 1Mb of kernel memory.  Windows no longer in use will have this memory reclaimed by the system as is feasible.

   What Are the Side Effects of Raising the Value?
       A little more memory is used in the kernel.

   When Should the Value of This Tunable Be Lowered?
       If  process  groups are not being used, or not being used in the quantity set by the tunable, there is really no point to having this value
       higher than what is actually needed.

   What Are the Side Effects of Lowering the Value?
       The kernel uses a little less memory.  If the value is set to no group-private Q3's are allowed.

   What Other Tunable Values Should Be Changed at the Same Time?
       None.

WARNINGS

       All HP-UX kernel tunable parameters are release specific.  This parameter may be removed or have its meaning changed in future releases	of
       HP-UX.

       Installation  of  optional  kernel  software, from HP or other vendors, may cause changes to tunable parameter values.  After installation,
       some tunable parameters may no longer be at the default or recommended values.  For information about the effects of installation  on  tun-
       able  values,  consult  the documentation for the kernel software being installed.  For information about optional kernel software that was
       factory installed on your system, see at

AUTHOR

       was developed by HP.

SEE ALSO

       getmemwindow(1M), setmemwindow(1M), services.window(4).

							     Tunable Kernel Parameters						 max_mem_window(5)