From: Vlastimil Babka <vbabka@suse.cz>
To: Arthur Marsh <arthur.marsh@internode.on.net>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: difficult to pinpoint exhaustion of swap between 4.2.0-rc6 and 4.2.0-rc7
Date: Fri, 21 Aug 2015 13:48:49 +0200 [thread overview]
Message-ID: <55D71021.7030803@suse.cz> (raw)
In-Reply-To: <55D70D80.5060009@suse.cz>
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, 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>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Arthur Marsh <arthur.marsh@internode.on.net>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: difficult to pinpoint exhaustion of swap between 4.2.0-rc6 and 4.2.0-rc7
Date: Fri, 21 Aug 2015 13:48:49 +0200 [thread overview]
Message-ID: <55D71021.7030803@suse.cz> (raw)
In-Reply-To: <55D70D80.5060009@suse.cz>
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.
next prev parent reply other threads:[~2015-08-21 11:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 15:44 difficult to pinpoint exhaustion of swap between 4.2.0-rc6 and 4.2.0-rc7 Arthur Marsh
2015-08-19 15:44 ` Arthur Marsh
2015-08-20 8:16 ` Vlastimil Babka
2015-08-20 8:16 ` Vlastimil Babka
2015-08-21 9:17 ` Arthur Marsh
2015-08-21 11:37 ` Vlastimil Babka
2015-08-21 11:37 ` Vlastimil Babka
2015-08-21 11:48 ` Vlastimil Babka [this message]
2015-08-21 11:48 ` Vlastimil Babka
2015-08-21 12:43 ` Arthur Marsh
2015-08-21 12:43 ` Arthur Marsh
2015-08-22 4:48 ` Arthur Marsh
2015-08-22 4:48 ` Arthur Marsh
2015-08-22 7:05 ` Vlastimil Babka
2015-08-22 7:05 ` Vlastimil Babka
2015-08-21 12:38 ` Arthur Marsh
2015-08-21 12:38 ` Arthur Marsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55D71021.7030803@suse.cz \
--to=vbabka@suse.cz \
--cc=arthur.marsh@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.