You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Xiao-Feng Li <xi...@gmail.com> on 2009/07/02 08:46:31 UTC
[GSoC] it is time for mid-time project checking
Simon, what's your progress?
Thanks,
xiaofeng
--
http://people.apache.org/~xli
Re: [GSoC] it is time for mid-time project checking
Posted by Xiao-Feng Li <xi...@gmail.com>.
Simon, thanks. The progress looks good. It would be great if you can
submit your patch to JIRA so that it is visible to the community.
Thanks,
xiaofeng
On Sun, Jul 5, 2009 at 6:02 PM, Simon Zhou<si...@gmail.com> wrote:
> Hi, Xiaofeng,
> Sorry for late replay, I just have moved to a new renting room recent days,
> the network is just connected.
> I think I have finished first 2 parts of this project.
> DONE:
> In step 0, I find the cause of problem of barrier generating, xiaoming helps
> me on this issue and give a solution.
> In step 1, I implemented 2 version of barrier for get() method, one is
> simply using a JNI call to invoke a GC method. Another version is a vmmagic
> version, my 'get() barrier' implementation just follows the approach of
> implementing write barrier.
> In step 2, I modified the concurrent marker to support weak reference
> processing, markers threads will put the reference object to a
> list according to its type. when the concurrent marking finishes, I use the
> last marker thread to process soft/weak reference lists, concurrently
> (Because this process do not impact the object referencing graph).
> Now, I am thinking of a improving, need we make the weak/soft reference
> processing parallel?
> TODO:
> In step 3, I will implement a STW phase for finalizable objects and phantom
> reference processing. In this phase, gc thread will trace from the dead
> objects in the list to resurrect all reachable objects from them. this phase
> will change the object referencing graph, so it should be dealt in a STW
> manner.
> I am starting writing the formal mid-term status report today, is there
> anything I should pay more attention to in this report?
> Thank you!
> Simon
> Thanks
>
> 2009/7/2 Xiao-Feng Li <xi...@gmail.com>
>>
>> Simon, what's your progress?
>>
>> Thanks,
>> xiaofeng
>>
>> --
>> http://people.apache.org/~xli
>
>
>
> --
> From : Simon.Zhou@PPI, Fudan University
>
--
http://people.apache.org/~xli
Re: [GSoC] it is time for mid-time project checking
Posted by Xiao-Feng Li <xi...@gmail.com>.
Simon, I've read your patch in
https://issues.apache.org/jira/browse/HARMONY-6258. It looks good to
me.
Please go continuing with your great work!
Thanks,
xiaofeng
On Sun, Jul 5, 2009 at 6:02 PM, Simon Zhou<si...@gmail.com> wrote:
> Hi, Xiaofeng,
> Sorry for late replay, I just have moved to a new renting room recent days,
> the network is just connected.
> I think I have finished first 2 parts of this project.
> DONE:
> In step 0, I find the cause of problem of barrier generating, xiaoming helps
> me on this issue and give a solution.
> In step 1, I implemented 2 version of barrier for get() method, one is
> simply using a JNI call to invoke a GC method. Another version is a vmmagic
> version, my 'get() barrier' implementation just follows the approach of
> implementing write barrier.
> In step 2, I modified the concurrent marker to support weak reference
> processing, markers threads will put the reference object to a
> list according to its type. when the concurrent marking finishes, I use the
> last marker thread to process soft/weak reference lists, concurrently
> (Because this process do not impact the object referencing graph).
> Now, I am thinking of a improving, need we make the weak/soft reference
> processing parallel?
> TODO:
> In step 3, I will implement a STW phase for finalizable objects and phantom
> reference processing. In this phase, gc thread will trace from the dead
> objects in the list to resurrect all reachable objects from them. this phase
> will change the object referencing graph, so it should be dealt in a STW
> manner.
> I am starting writing the formal mid-term status report today, is there
> anything I should pay more attention to in this report?
> Thank you!
> Simon
> Thanks
>
> 2009/7/2 Xiao-Feng Li <xi...@gmail.com>
>>
>> Simon, what's your progress?
>>
>> Thanks,
>> xiaofeng
>>
>> --
>> http://people.apache.org/~xli
>
>
>
> --
> From : Simon.Zhou@PPI, Fudan University
>
--
http://people.apache.org/~xli
Re: [GSoC] it is time for mid-time project checking
Posted by Simon Zhou <si...@gmail.com>.
Hi, Xiaofeng,
Sorry for late replay, I just have moved to a new renting room recent days,
the network is just connected.
I think I have finished first 2 parts of this project.
DONE:
In step 0, I find the cause of problem of barrier generating, xiaoming helps
me on this issue and give a solution.
In step 1, I implemented 2 version of barrier for get() method, one is
simply using a JNI call to invoke a GC method. Another version is a vmmagic
version, my 'get() barrier' implementation just follows the approach of
implementing write barrier.
In step 2, I modified the concurrent marker to support weak reference
processing, markers threads will put the reference object to a
list according to its type. when the concurrent marking finishes, I use the
last marker thread to process soft/weak reference lists, concurrently
(Because this process do not impact the object referencing graph).
Now, I am thinking of a improving, need we make the weak/soft reference
processing parallel?
TODO:
In step 3, I will implement a STW phase for finalizable objects and phantom
reference processing. In this phase, gc thread will trace from the dead
objects in the list to resurrect all reachable objects from them. this phase
will change the object referencing graph, so it should be dealt in a STW
manner.
I am starting writing the formal mid-term status report today, is there
anything I should pay more attention to in this report?
Thank you!
Simon
Thanks
2009/7/2 Xiao-Feng Li <xi...@gmail.com>
> Simon, what's your progress?
>
> Thanks,
> xiaofeng
>
> --
> http://people.apache.org/~xli
>
--
>From : Simon.Zhou@PPI, Fudan University