About the configuration setting of externalMemoryManagementEnabled

[skane1024]

I noticed there is a configuration option in INetworkProperties called m_ExternalMemoryManagementEnabled, its default value is False. I don't quite understand what it means. Does it refer to different backends using external unified memory management? I've tried setting externalMemoryManagementEnabled to True on some models, and found that several models have segment fault errors. I haven't seen this feature introduced in the documentation or test code, I just found it in the code. Is this feature usable? I hope you can help me clear up my confusion.

[tracyn-arm]

Hi. I did a code search and the m_ExternalMemoryManagementEnabled class variable looks like an orphaned flag. I commented it out and removed its references in IRuntime.hpp and Arm NN still built and ran. So I am unsure why you would encounter segfaults when you set this variable to true. If you see something different then please let us know.

One last thing though is that there is a related backend option "ExternallyManagedMemory" that seems to be on by default in a number of cases:

    src/backends/reference/RefBackend.hpp: {"ExternallyManagedMemory", true},
    src/backends/neon/NeonBackend.hpp: {"ExternallyManagedMemory", true},
    src/backends/cl/ClBackend.cpp: {"ExternallyManagedMemory", true},

Thanks.