harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Volosyuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-2907) [drlvm][gc] re-enabling of pinning in gcv4.1
Date Wed, 10 Jan 2007 15:17:27 GMT

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

Ivan Volosyuk commented on HARMONY-2907:

New patch fixes a few inconsistencies:
  An assert() statement removed from selector.cpp which may no longer hold.
  Last word reserved should be GC_OBJECT_ALIGNMENT long. 

> [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
> 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


View raw message