On Thu, Oct 24, 2019 at 12:34:41PM +0800, Qian Cai wrote: > > > > On Oct 23, 2019, at 11:33 PM, Feng Tang <feng.tang@xxxxxxxxx> wrote: > > > > We have been using the /proc/pagetypeinfo for debugging, mainly for > > client platforms like phones/tablets. We met problems like very slow > > system response or OOM things, and many of them could be related with > > memory pressure or fragmentation issues, where monitoring /proc/pagetypeinfo > > will be very useful for debugging. > > This description of use case is rather vague. Which part of the information in that file is critical to debug an OOM or slow system that is not readily available in places like /proc/zoneinfo, /proc/buddyinfo, sysrq-m, or OOM trace etc? One example is, there was a platform with limited DRAM, so it preset some CMA memory for camera's big buffer allocation use, while it let these memory to be shared by others when camera was not used. And after long time running, the cma region got fragmented and camera app started to fail due to the buffer allocation failure. And during debugging, we kept monitoring the buddy info for different migrate types. Thanks, Feng
