VMS Help
V73 Features, System Management Features, Dedicated CPU Lock Manager (Alpha), Using with Affinity

 *Conan The Librarian (sorry for the slow response - running on an old VAX)

    The LCKMGR_SERVER process uses the affinity mechanism to set
    the process to the lowest CPU ID other than the primary. You can
    change this by indicating another CPU ID with the LCKMGR_CPUID
    system parameter. The Dedicated CPU Lock Manager then attempts
    to use this CPU. If this CPU is not available, it reverts back to
    the lowest CPU other than the primary.

    The following shows how to dynamically change the CPU used by the
    LCKMGR_SERVER process:

    $RUN SYS$SYSTEM:SYSGEN
    SYSGEN>USE ACTIVE
    SYSGEN>SET LCKMGR_CPUID 2
    SYSGEN>WRITE ACTIVE
    SYSGEN>EXIT
 To verify the CPU dedicated to the lock manager, use the following
 show system command:

    $ SHOW SYSTEM/PROCESS=LCKMGR_SERVER

    This change applies to the currently running system. A reboot
    reverts back to the lowest CPU other than the primary. To
    permanently change the CPU used by the LCKMGR_SERVER process,
    set LCKMGR_CPUID in your MODPARAMS.DAT file.

    Compaq highly recommends that a process not be given hard
    affinity to the CPU used by the Dedicated CPU Lock Manager.
    With hard affinity when such a process becomes computable, it
    cannot obtain any CPU time, because the LCKMGR_SERVER process
    is running at the highest possible real-time priority of 63.
    However, the LCKMGR_SERVER detects once per second if there are
    any computable processes that are set by the affinity mechanism
    to the dedicated lock manager CPU. If so, the LCKMGR_SERVER
    switches to a different CPU for one second to allow the waiting
    process to run.
  Close     HLB-list     TLB-list     Help  

[legal] [privacy] [GNU] [policy] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.