nonmoving: Refactor update remembered set initialization
This avoids a lock inversion between the storage manager mutex and the stable pointer table mutex by not dropping the SM_MUTEX in nonmovingCollect. This requires quite a bit of rejiggering but it does seem like a better strategy.
Showing
- rts/sm/GC.c 2 additions, 7 deletionsrts/sm/GC.c
- rts/sm/NonMoving.c 10 additions, 4 deletionsrts/sm/NonMoving.c
- rts/sm/NonMovingMark.c 51 additions, 19 deletionsrts/sm/NonMovingMark.c
- rts/sm/NonMovingMark.h 2 additions, 3 deletionsrts/sm/NonMovingMark.h
- rts/sm/Storage.c 1 addition, 1 deletionrts/sm/Storage.c
Loading
Please register or sign in to comment