Thanks for your reply,
We already used other i/f like page_owner and kmemleak to resolve memory
leakage issue.
But, page_owner can only for guess but cannot find intuitively memory
usage regarding page_frag_cache.
And kmemleak cannot use (because of calling directly
__alloc_pages_nodemask()).
Additionally, some embedded linux like Android or something..
is not able to always use kmemleak & page_owner because of runtime
performance deterioration.
However, the root cause of this memory issue is from net device like
wireless.
In short, should always use wireless on device but, cannot use those
memory debug tools.
That's why those counters need..
and for much cheaper I can remove pgfrag_alloc_calls and pgfrag_free_calls.
Thanks,
Kyeongdon Kim
On 2017-09-01 오후 6:21, Michal Hocko wrote:
On Fri 01-09-17 12:12:36, Konstantin Khlebnikov wrote:
> IMHO that's too much counters.
> Per-node NR_FRAGMENT_PAGES should be enough for guessing what's
going on.
> Perf probes provides enough features for furhter debugging.
I would tend to agree. Adding a counter based on a single debugging
instance sounds like an overkill to me. Counters should be pretty cheep
but this is way too specialized API to export to the userspace.
We have other interfaces to debug memory leaks like page_owner.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
