Re: tracking memory usage/leak in "inactive" field in /proc/meminfo?

[Rik van Riel]

On 02/16/2010 04:26 PM, Chris Friesen wrote:

> For the backtrace scenario I posted it seems like it might actually be
> release_pages().  There seems to be a plausible call chain:
>
> __ClearPageLRU
> release_pages
> free_pages_and_swap_cache
> tlb_flush_mmu
> tlb_remove_page
> zap_pte_range
>
> Does that seem right?  In this case, tlb_remove_page() is called right
> after page_remove_rmap() which ultimately results in clearing the
> PageAnon bit.

That is right - and pinpoints the fault for the memory leak
on some third party code that fails to release a refcount on
memory pages.

--
All rights reversed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/