You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Pavel Rebriy (JIRA)" <ji...@apache.org> on 2007/10/01 08:22:50 UTC

[jira] Updated: (HARMONY-4830) [drlvm][thread] explicit allocation/deallocation of thread native resources

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

Pavel Rebriy updated HARMONY-4830:
----------------------------------

    Attachment: tm_explicit_allocatetion_deallocation_VM_thread.patch

An updated patch.
- Fixed stress.Mix hang
- Fixed hythread_get_os_id() compilation of WinXP
- Improved performance of hythread_suspend_disable()


> [drlvm][thread] explicit allocation/deallocation of thread native resources
> ---------------------------------------------------------------------------
>
>                 Key: HARMONY-4830
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4830
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>            Reporter: Pavel Rebriy
>            Assignee: weldon washburn
>         Attachments: tm_explicit_allocatetion_deallocation_VM_thread.patch
>
>
> The issue is the final part of Thread Life Cycle redesign.
> The main goal of the issue is to implement explicit allocation and deallocation of thread native resources. Current version of TM reuses native resources, it could be a result of OOM in native heap. Explicit allocation/deallocation simplifies Thread Block Life Circle, improves maintainability of TM code and prevents OOM in native heap.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.