IBM Support

VM65696: SCHEDULER LOCK IMPROVEMENTS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Poor system performance in large N-way partitions due to
    cache alignment of the scheduler lock and nearby fields.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/VM                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    Customers might experience decreased performance due to
    the location of the scheduler lock (SRMSLOCK).  The allocation
    of the SRMBK provides no cache boundary alignment, so it is
    indeterminate exactly which other fields in the SRMBK will
    happen to be in the same cache line as SRMSLOCK.
    
    Interference from reads/writes to other data in the same cache
    line can reduce the efficiency with which the control program
    (CP) can manage the scheduler lock.
    

Problem conclusion

  • The code which allocates the SRMBK is modified to allocate an
    entire page of memory for the SRMBK, thus assuring cache
    boundary alignment.  The scheduler lock (SRMSLOCK) is relocated
    to a new displacement within the SRMBK such that there are no
    other fields within the same cache line and thus no interference
    from accesses of those fields by other processors.
    
    Further, the SRMSLOCK is split so that the spin lock area
    (SYNBK) occupies the very end of a cache line, while the spin
    lock extension area (SYNBX) follows contiguously at the start
    of the next cache line.  This alignment maintains the
    requirement of these two sections being contiguous.  However,
    by being located in two separate cache lines, updates that
    spinning CPUs make to masks and statistics located in the SYNBX
    do not interfere with CPUs which are trying to update the SYNBK.
    

Temporary fix

Comments

APAR Information

  • APAR number

    VM65696

  • Reported component name

    VM CP

  • Reported component ID

    568411202

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-05

  • Closed date

    2015-03-23

  • Last modified date

    2016-03-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UM34572

Modules/Macros

  • CBITABLE HCPAFF   HCPALF   HCPALL   HCPALR
    HCPAPJ   HCPCBI   HCPCFM   HCPCPA   HCPCPU   HCPCSA   HCPDSB
    HCPDSP   HCPHIP   HCPHRU   HCPHTF   HCPISR   HCPLGN   HCPLMC
    HCPMCI   HCPMCS   HCPMCW   HCPMOL   HCPMPC   HCPMPS   HCPMTF
    HCPMTO   HCPMTS   HCPPPI   HCPPTE   HCPPTF   HCPPTG   HCPQDO
    HCPRLG   HCPRLU   HCPSCI   HCPSCJ   HCPSGP   HCPSHI   HCPSNR
    HCPSRM   HCPSRMBK HCPSRN   HCPSSI   HCPSTK   HCPSTL   HCPSTM
    HCPSTP   HCPSXP   HCPTHQ   HCPWAI   HCPZPQ
    

Fix information

  • Fixed component name

    VM CP

  • Fixed component ID

    568411202

Applicable component levels

  • R630 PSY UM34572

       UP15/03/24 P 1601

  • R540 PSN

       UP

  • R620 PSN

       UP

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
30 March 2016