You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Xiao-Feng Li (JIRA)" <ji...@apache.org> on 2008/01/17 06:44:34 UTC

[jira] Closed: (HARMONY-2907) [drlvm][gc_cc] re-enabling of pinning in gcv4.1

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

Xiao-Feng Li closed HARMONY-2907.
---------------------------------

    Resolution: Won't Fix

> [drlvm][gc_cc] 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
>            Assignee: Xiao-Feng Li
>            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.
-
You can reply to this email to add a comment to the issue online.