harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Rebriy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4830) [drlvm][thread] explicit allocation/deallocation of thread native resources
Date Thu, 20 Sep 2007 13:13:31 GMT

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

Pavel Rebriy commented on HARMONY-4830:
---------------------------------------

Current functionality of Thread State Transition is based on mixing java and native recourses.
Thats why java and native recourses interaction prevents of implementation of explicit deallocation
of native resources. As en example j.l.Thread.isInterrupted() or j.l.Thread.interrupt() functions
use native thread structure even for dead java thread.

To implement explicit deallocation need to separate usage of java thread resources and native
thread. This topic is closely discussed in HARMONY-4716.

In such a way the primary goal is to implement explicit allocation of native thread structure,
deallocation can be implemented after Thread State Transition refactoring.


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


Mime
View raw message