You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Xiao-Feng Li (JIRA)" <ji...@apache.org> on 2007/08/04 15:44:53 UTC

[jira] Commented: (HARMONY-4601) [drlvm][gc_gen] Thread termination in thread.SmallStackThreadTest is terribly slow

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

Xiao-Feng Li commented on HARMONY-4601:
---------------------------------------

This issue is not a bug. It depends on TM's design for thread
destruction. As I understand, Weldon suggested to serialized the
process of thread termination/creation in TM. The gc_thread_kill
should be invoked in the serialization part. If that's true, the spin
lock can be removed. I put the spin lock there because TM redesign is
not finished. When it's done, we will remove the spin lock, but then
it's TM's responsibility to invoke gc_thread_kill at proper moment.

Thanks,
xiaofeng



-- 
http://xiao-feng.blogspot.com


> [drlvm][gc_gen] Thread termination in thread.SmallStackThreadTest is terribly slow
> ----------------------------------------------------------------------------------
>
>                 Key: HARMONY-4601
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4601
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux/ia32
>            Reporter: Gregory Shimansky
>
> The test creates a big number of threads (4000) that mostly do nothing. Threads are waiting and then are joined by the main thread. This mostly doesn't consume CPU on the machine. But then all of these threads go through gc_thread_kill function. It executes thread deletion from a list under a global spin-lock, so all 4000 threads are waiting on it using CPU at the same time since the lock spins inside of the loop.
> This test usually doesn't finish on linux/ia32 (for some reason it works on other platforms) and times out. So I created this bug report to exclude it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.