Quantcast
Channel: Embedded Software (Read Only)
Viewing all articles
Browse latest Browse all 25965

Forum Post: RE: VoLIB Multichannel Memory Usage and Specific Module Implementations

$
0
0

I think I was too broad and open-ended in my original post. Specifically for now, I'm interested in the wording used in the documentation for the VoLIB modules. Each module shows memory usage in tables that are labelled per instance. In these tables are scratch buffers and dedicated buffers. Can the scratch buffers be shared between instances and if not, do they need to remain untouched between subsequent processing calls for a given channel? (I'm confused on the wording of scratch vs dedicated in a table labelled per instance data buffers)

One other question in the same line. Most of the modules use their own heap memory implementation. I assume the sizes are based on some X number of channels. If I want to use more or less channels, I assume I can just change the size of the buffers used for heap memory. Is there any reason to use these heap memory implementations over standard malloc()/free() calls? TDU for instance doesn't use its own heap memory implementation is there any reason why it wouldn't work with its own heap memory implementation rather than the malloc()/free() calls?

Regards,

Chris


Viewing all articles
Browse latest Browse all 25965

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>