-
Notifications
You must be signed in to change notification settings - Fork 13
Considerations on memory management #287
Comments
#292 Deals with issue 2 by deleting the cached version since we've agreed previously to not use the caching allocator here. Both will actually be deleted when that area of the code moves to Alpaka since the buffers are freed automatically. It also deals with issue 1, moving the allocation to module.cu. |
More instances of variables in global scope (sub-issue 3 above): Lines 5 to 9 in 6e6e2d0
TrackLooper/SDL/ModuleConnectionMap.cc Lines 3 to 24 in 6e6e2d0
|
One more instance of variables in global scope (sub issue 3 like mentioned above): TrackLooper/SDL/TiltedGeometry.cc Line 3 in c58c36e
|
@GNiendorf subissue 3 is still open but was subissue 1 dealt with during the Alpaka migration? |
@VourMa Yup, subissue 1 is fixed! |
Given that we found a work-around for thread-safety of global variables, should we close this issue? |
I think that |
@slava77 @GNiendorf Is subissue 3 of this issue closed by the #377? |
do you mean
? Well, they are still in a "global" space in |
I think this can be closed now, right @VourMa? |
I would say so, yes. Closing and we can reopen a new, more dedicated one if we see anymore problems. |
While investigating issue #285, I came across a couple of points in our code where the memory allocations seemed a bit weird/bug-prone. Let me mention them below, so that more people can take a look and let me know if I am missing something:
1. The allocation of the
indicesOfEligibleT5Modules
happens inEvent.cu
TrackLooper/SDL/Event.cu
Lines 1257 to 1261 in 4d0158d
Module.cu
TrackLooper/SDL/Module.cu
Line 12 in 4d0158d
TrackLooper/SDL/Module.cu
Line 108 in 4d0158d
Module.cu
.2. We have only one way to allocate the modulesInGPU
TrackLooper/SDL/Module.cu
Lines 76 to 106 in 4d0158d
TrackLooper/SDL/Module.cu
Lines 166 to 203 in 4d0158d
TrackLooper/SDL/Module.cu
Lines 204 to 244 in 4d0158d
3. Finally, I would like to ask why these variables
TrackLooper/SDL/Event.cu
Lines 4 to 7 in 4d0158d
Event
class or defined in the appropriate file where they are relevant.The text was updated successfully, but these errors were encountered: