You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Aleksey Ignatenko (JIRA)" <ji...@apache.org> on 2006/11/13 07:07:37 UTC

[jira] Created: (HARMONY-2158) native resource cleanup

native resource cleanup 
------------------------

                 Key: HARMONY-2158
                 URL: http://issues.apache.org/jira/browse/HARMONY-2158
             Project: Harmony
          Issue Type: Improvement
          Components: DRLVM
            Reporter: Aleksey Ignatenko


Current implementation of DrlVM implies common code pool for all jitted code. There are disadvantages of that approach: common lock for all allocation operations, no possibility to free memory of jitted code in case when there is class unloading happent. 


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

        

[jira] Assigned: (HARMONY-2158) native resource cleanup

Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HARMONY-2158?page=all ]

weldon washburn reassigned HARMONY-2158:
----------------------------------------

    Assignee: weldon washburn

> native resource cleanup
> -----------------------
>
>                 Key: HARMONY-2158
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2158
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Aleksey Ignatenko
>         Assigned To: weldon washburn
>         Attachments: cleanup_sources_1558_merged.patch
>
>
> Current implementation of DrlVM implies common code pool for all jitted code. There are disadvantages of that approach: common lock for all allocation operations, no possibility to free memory of jitted code in case when there is class unloading happent. 

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

        

[jira] Updated: (HARMONY-2158) native resource cleanup

Posted by "Aleksey Ignatenko (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HARMONY-2158?page=all ]

Aleksey Ignatenko updated HARMONY-2158:
---------------------------------------

    Attachment: cleanup_sources_1558_merged.patch

The patch contains the following issues solved:
1. Gloval jitted code pool is divided into separate pools attached to appropriate classloaders (jitted code, jb=ni and compileme stubs are allocated from pools of appropriated classloaders). 
2. introduced interface to be able to allocated GC related memory from classloader's pools.
3. Introduced cleanup in method_lookup_table (if class unloading is done then global method_lookup_table must be cleaned for corresponding items to prevent crashes).
4. Introduced unloading of native library used to load native jni method in case of appropriate classloader is unloaded.
4. Some code cleanup done.

> native resource cleanup
> -----------------------
>
>                 Key: HARMONY-2158
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2158
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Aleksey Ignatenko
>         Attachments: cleanup_sources_1558_merged.patch
>
>
> Current implementation of DrlVM implies common code pool for all jitted code. There are disadvantages of that approach: common lock for all allocation operations, no possibility to free memory of jitted code in case when there is class unloading happent. 

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

        

[jira] Commented: (HARMONY-2158) native resource cleanup

Posted by "Aleksey Ignatenko (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/HARMONY-2158?page=comments#action_12450694 ] 
            
Aleksey Ignatenko commented on HARMONY-2158:
--------------------------------------------

I going to check the patch on em64t which was restored recently. Work is in progress.

> native resource cleanup
> -----------------------
>
>                 Key: HARMONY-2158
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2158
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Aleksey Ignatenko
>         Assigned To: weldon washburn
>         Attachments: cleanup_sources_1558_merged.patch
>
>
> Current implementation of DrlVM implies common code pool for all jitted code. There are disadvantages of that approach: common lock for all allocation operations, no possibility to free memory of jitted code in case when there is class unloading happent. 

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