Subject: Re: difficult to pinpoint exhaustion of swap between 4.2.0-rc6 and
 4.2.0-rc7
To: Arthur Marsh <arthur.marsh@internode.on.net>, linux-mm@kvack.org
References: <55D4A462.3070505@internode.on.net> <55D58CEB.9070701@suse.cz>
 <55D6ECBD.60303@internode.on.net> <55D70D80.5060009@suse.cz>
Cc: linux-kernel@vger.kernel.org,
        Linus Torvalds <torvalds@linux-foundation.org>
From: Vlastimil Babka <vbabka@suse.cz>
Message-ID: <55D71021.7030803@suse.cz>
Date: Fri, 21 Aug 2015 13:48:49 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <55D70D80.5060009@suse.cz>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 916
Lines: 21

On 08/21/2015 01:37 PM, Vlastimil Babka wrote:
>
> That, said, looking at the memory values:
>
> rc6: Free+Buffers+A/I(Anon)+A/I(File)+Slab = 6769MB
> rc7: ...                                   = 4714MB
>
> That's 2GB unaccounted for.

So one brute-force way to see who allocated those 2GB is to use the 
page_owner debug feature. You need to enable CONFIG_PAGE_OWNER and then 
follow the Usage part of Documentation/vm/page_owner.txt
If you can do that, please send the sorted_page_owner.txt for rc7 when 
it's semi-nearing the exhausted swap. Then you could start doing a 
comparison run with rc6, but maybe it will be easy to figure from the 
rc7 log already. Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/