harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Afremov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-2560) Finalizer and weak reference for GCv5
Date Mon, 11 Dec 2006 11:24:23 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-2560?page=comments#action_12457287 ] 
Pavel Afremov commented on HARMONY-2560:

Hi I have several questions about finalizer & ref in vm part.

1.       For what reason is native finalizer thread required? I thought that native and java
threads is equal for finalization purpose. Also Java thread can uses future "magic" technology
for extra performance.

2.       Finalizer thread starts works with highest priority, doesn't it? Is it right? Why
VM should stops when any finalization works is required?

3.       In Finalization system now there is Work Balance Mechanism which tunes performance
of finalization. When many finalizable object are allocated and queue for finalization isn't
empty this mechanism increase performance of finalization (more detailed description see in
dev guide). I can't found usage of Work Balance Subsystem in this patch. Maybe it would be
better to use WBS instead high priority forever for finalizer thread.

4.       Did you check you patch with gc.SynchronizedFinalizerTest? Could play with parameters
in this synthetic stress test to provide reliability of finalization system for any work load.


Thank you in advance

Pavel Afremov.

> Finalizer and weak reference for GCv5
> -------------------------------------
>                 Key: HARMONY-2560
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2560
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>         Environment: Windows and Linux 32-bit
>            Reporter: Li-Gang Wang
>         Assigned To: weldon washburn
>         Attachments: finalizer_weakref_for_GCv5_061210.patch, finalizer_weakref_for_GCv5_20061210.patch
> This patch implements finalizer and weak reference functions for GCv5.
> The finalizer threads are implemented as native threads. And weak reference enqueueing
is also executed in a native thread. But these features will not affect the present implementation
at all. They are only used for GCv5.
> To apply this patch, please firstly apply this patch:
> https://issues.apache.org/jira/browse/HARMONY-2509
> Then enter "drlvm/trunk", "patch -p1 < finalizer_weakref_for_GCv5_20061210.patch"
> Files added in this patch include:
> drlvm/trunk/vm/vmcore/include/finalizer_thread.h
> drlvm/trunk/vm/vmcore/include/ref_enqueue_thread.h
> drlvm/trunk/vm/vmcore/src/init/finalizer_thread.cpp
> drlvm/trunk/vm/vmcore/src/init/ref_enqueue_thread.cpp
> drlvm/trunk/vm/gc_gen/src/finalizer_weakref/finalizer_weakref_metadata.h
> drlvm/trunk/vm/gc_gen/src/finalizer_weakref/finalizer_weakref_metadata.cpp
> drlvm/trunk/vm/gc_gen/src/finalizer_weakref/finalizer_weakref.h
> drlvm/trunk/vm/gc_gen/src/finalizer_weakref/finalizer_weakref.cpp

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


View raw message