[ovs-discuss] ovs-vswitchd memory consumption behavior

Fernando Casas Schössow casasfernando at outlook.com
Tue Mar 19 23:56:42 UTC 2019


The guys from musl confirmed ASan will not work with musl there are known issues.

[00:13] <@dalias> the asan runtime doesn't work with musl afaik. it's very invasive and i'm not sure what would take to make it work
[00:14] <nsz> yeah it does not work
[00:18] <@dalias> it could just be the issue with musl's malloc wrongly enlarging the heap under heavy contention
[00:18] <nsz> musl supports malloc interposition nowadays, so you can try another allocator maybe
[00:18] <@dalias> *nod*
[00:19] <nsz> try ldpreloading jemalloc or tcmalloc and see if the problem disappears

Problem is jemalloc nor tcmalloc are available on Alpine out of the box.

So I will check if I can compile jemalloc and test OVS using ld preloading as suggested.

On mar, mar 19, 2019 at 7:18 PM, Fernando Casas Schössow <casasfernando at outlook.com> wrote:
I discussed this with one of Alpine developers and it's not clear that ASan works with musl.

Also opened an issue to Alpine about this to see if I can get also some help from their side:

https://bugs.alpinelinux.org/issues/10138

I will check in musl developers IRC channel to try to confirm if using ASan is an option or I will be wasting my time. :(

On mar, mar 19, 2019 at 8:13 AM, Fernando Casas Schössow <casasfernando at outlook.com> wrote:
Not yet. I will look into how to do it in Alpine.

On lun, mar 18, 2019 at 10:37 PM, Ben Pfaff <blp at ovn.org> wrote:
Did you try compiling with Address Sanitizer yet? It is just as effective as valgrind at finding leaks, but it slows the process much less than valgrind does, so it is less likely to change behavior due to timing issues.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190319/09b3c660/attachment.html>


More information about the discuss mailing list