harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Rogers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-6257) [classlib][luni] - Optimize OSMemory.get/setByteArray
Date Tue, 07 Jul 2009 08:34:14 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727983#action_12727983
] 

Ian Rogers commented on HARMONY-6257:
-------------------------------------

Previously there has been discussion of adding support so that MMTk could be used as a GC
for DRLVM, but I don't think it has happened. I'm also not sure that vmmagic is the correct
API, certainly the recent VEE paper didn't compare it with the models in the JNA (Java Native
Access) and the Maxine VM (which reinvents this API). I believe they may have compared with
the Unsafe API. I think it's worth noting there is quite a bit of redundancy in having all
these interfaces which increases the burden of migrating Harmony (in a performant way).

> [classlib][luni] - Optimize OSMemory.get/setByteArray
> -----------------------------------------------------
>
>                 Key: HARMONY-6257
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6257
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>    Affects Versions: 5.0M10
>            Reporter: Regis Xu
>         Attachments: HARMONY-6257.diff
>
>
> in getByteArray, use SetByteArrayRegion to avoid memory copy from java to native
> in setByteArray, Get/ReleasePrimitiveArrayCritical instead of GetByteArrayElements/ReleaseByteArrayElements
to avoid memory copy.

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