[erlang-questions] Memsup is still broken under Linux

24 views
Skip to first unread message

Dmitry Groshev

unread,
Nov 16, 2011, 7:58:00 AM11/16/11
to erlang-q...@erlang.org
This issue http://erlang.org/pipermail/erlang-questions/2006-September/023135.html
is at least 5 years old, it's obvious, it ruins memsup usage under
Linux and it's trivial to fix. Is there any problems with fixing it
that I can't see? If not, why it wasn't fixed yet?
_______________________________________________
erlang-questions mailing list
erlang-q...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

Björn-Egil Dahlberg

unread,
Nov 16, 2011, 8:22:51 AM11/16/11
to erlang-q...@erlang.org
There are extra tags describing cached and buffered memory.

7> memsup:get_system_memory_data().
[{system_total_memory,8322506752},
{free_swap,7939817472},
{total_swap,7999582208},
{cached_memory,3634323456},
{buffered_memory,521039872},
{free_memory,990232576},
{total_memory,8322506752}]

we cannot change the meaning of free_memory tag.

// Björn-Egil

Dmitry Groshev

unread,
Nov 17, 2011, 7:16:45 AM11/17/11
to erlang-pr...@googlegroups.com, erlang-q...@erlang.org
There was a proposal in that thread of returning an extra entry.
Reply all
Reply to author
Forward
0 new messages