README VERSION		: 1.0
README Creation Date	: 2012-02-08
Patch-ID 		: 143682-04 
Patch Name		: VRTSglm 5.1SP1RP2P1
BASE PACKAGE NAME	: VRTSglm
BASE PACKAGE VERSION	: 5.1
Obsolete Patches	: NONE
Superseded Patches	: 143682-03
Required Patches	: NONE
Incompatible Patches	: NONE
Supported PADV		: sol10_x86
(P-Platform , A-Architecture , D-Distribution , V-Version)
Patch Category		: OTHER
Reboot Required		: YES

Patch Installation Instructions:
--------------------------------
For Solaris 2.0-2.6 releases, refer to the Install.info file and/or
the README within the patch for instructions on using the generic
''installpatch'' and ''backoutpatch'' scripts provided with each patch.

For Solaris 7-9 releases, refer to the man pages for instructions
on using ''patchadd'' and ''patchrm'' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions.  The following example
installs a patch to a standalone machine:

       example# patchadd /var/spool/patch/143682-04



Patch Uninstallation Instructions:
----------------------------------
The following example removes a patch from a standalone system:

       example# patchrm 143682-04

For additional examples please see the appropriate man pages.


Special Instructions:
---------------------
NONE

KNOWN ISSUES : 


FIXED INCIDENTS: 
----------------


 Patch Id::143682-04

This GLM patch contains internal fix.

 Patch Id::143682-03

 * Incident no::2406572	 Tracking ID ::2146573

Symptom::Customer reported this as performance issue. The application was running slower
when this problem happens.
The SAR utility on HP-UX was showing some processes in PRI state.

Description::(1)	Complexity: This is an extremely complex performance concern in an  
environment where different applications are in great competition for the same 
system-wide resources.
(2)	Performance overheads: Competition for system resources is expected. 
However intense competition can create large overheads due to increased 
repetitive initialization. 

We approached this issue in multiple ways. Provided customer some tuning and
application changes.

Resolution::No product bug was identified from Symantec side. However a GLM patch was
provided to customer which does two things.

1. Different names given to different GLM spin locks. So that we can identify
various locks from spin watcher output.
2. We take avoiding a spinlock which keeps accounting if how many times
allocation did in GLM. Removing this lock will not cause any regression. Also,
we have not said that it will solve this performance problem.

 * Incident no::2554253	 Tracking ID ::2230240

Symptom::HP 5.1 SP1 GLMQA test hit an assert "Unaligned reference fault in kernel"
in internal testing.

Description::We are trying to access gm_range members from msg directly, which
are not 64-bit aligned.

Resolution::Fixing the unaligned access fault by using bcopy and then accessing
the struct members.

Incidents from old Patches:
---------------------------
NONE