This hasn't merged yet and was never the backend for malloc() or k_mem_pool, are you pulling it locally and writing code to its internal API?
toggle quoted messageShow quoted text
Have you tried a simple git bisect over your tree to look for other culprits?
On 10/5/19 6:58 AM, Christopher Friedt wrote:
Recently a sys_heap change went into zephyr
The PR says that it's faster, but I'm seeing some behaviour that would
suggest that's not the case.
The reason I bring it up, is that I had ported a certain protocol
subsystem over from an external repository (in my fork, atm). That
subsystem made heavy use of malloc. I rebased just a couple of days
ago (no other changes), and now I'm experiencing a fair amount of
timeouts when using the protocol that I did not experience before.
I've had to increase buffer sizes, etc.
Personally, I'm not a huge fan of malloc usage in communication code,
but I'm just kind of dealing with the code that I inherited.
Does anyone have some benchmarks on the new allocator? I'd really like
to have a look if that information is available.