Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <31001262.1169123969972.JavaMail.jira@brutus>
Date: Thu, 18 Jan 2007 04:39:29 -0800 (PST)
From: "Ivan Volosyuk (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-2907) [drlvm][gc] re-enabling of pinning
 in gcv4.1
In-Reply-To: <18575639.1167248543096.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465743 ] 

Ivan Volosyuk commented on HARMONY-2907:
----------------------------------------

New patch fixed win32 compilation warning about copy_alive() prototype.

> [drlvm][gc] re-enabling of pinning in gcv4.1
> --------------------------------------------
>
>                 Key: HARMONY-2907
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2907
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>         Environment: All
>            Reporter: Ivan Volosyuk
>            Priority: Minor
>         Attachments: h2907_pinning.diff, h2907_pinning2.diff, h2907_pinning3.diff
>
>
> Disabling of pinning of heap objects had negative performance impact for some work loads, like xml processing.
> Here is a patch to enable pinning again.
> Pinning support improved:
>  * added handling for pin counter overflow.
>  * hashcode status bits and pin counter has placed in different bytes of object status word to prevent any possibility of conflict
>  * pin counter updates are atomic while hashcode status updates are not.
> I have tested the code on following scenarios:
>    Live object is pinned in different threads and overflow pin counter
>    Objects are created and pinned in endless loop
>    Smoke tests
>    EM64T

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira