* [RFC] mm: shall we add an entry in meminfo to show the memory from module?
@ 2016-01-22 7:07 ` Xishi Qiu
0 siblings, 0 replies; 2+ messages in thread
From: Xishi Qiu @ 2016-01-22 7:07 UTC (permalink / raw)
To: Linux MM, LKML
Currently /proc/meminfo will not show the memory from module.
This entry "VmallocUsed: xxx" only shows the memory in the range
[VMALLOC_START, VMALLOC_END] alloced by vmalloc() ->... -> __vmalloc_node_range().
The memory which used by module is from module_alloc() -> __vmalloc_node_range().
So we will miss some memory when we calculate the total in meminfo.
Thanks,
Xishi Qiu
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [RFC] mm: shall we add an entry in meminfo to show the memory from module?
@ 2016-01-22 7:07 ` Xishi Qiu
0 siblings, 0 replies; 2+ messages in thread
From: Xishi Qiu @ 2016-01-22 7:07 UTC (permalink / raw)
To: Linux MM, LKML
Currently /proc/meminfo will not show the memory from module.
This entry "VmallocUsed: xxx" only shows the memory in the range
[VMALLOC_START, VMALLOC_END] alloced by vmalloc() ->... -> __vmalloc_node_range().
The memory which used by module is from module_alloc() -> __vmalloc_node_range().
So we will miss some memory when we calculate the total in meminfo.
Thanks,
Xishi Qiu
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-01-22 7:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-22 7:07 [RFC] mm: shall we add an entry in meminfo to show the memory from module? Xishi Qiu
2016-01-22 7:07 ` Xishi Qiu
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.