From: Michal Hocko <mhocko@kernel.org>
To: Matthias Dahl <ml_linux-kernel@binary-island.eu>
Cc: linux-raid@vger.kernel.org, linux-mm@kvack.org,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
Date: Wed, 13 Jul 2016 14:18:28 +0200 [thread overview]
Message-ID: <20160713121828.GI28723@dhcp22.suse.cz> (raw)
In-Reply-To: <20160713112126.GH28723@dhcp22.suse.cz>
On Wed 13-07-16 13:21:26, Michal Hocko wrote:
> On Tue 12-07-16 16:56:32, Matthias Dahl wrote:
[...]
> > If that support is baked into the Fedora provided kernel that is. If
> > you could give me a few hints or pointers, how to properly do a allocator
> > trace point and get some decent data out of it, that would be nice.
>
> You need to have a kernel with CONFIG_TRACEPOINTS and then enable them
> via debugfs. You are interested in kmalloc tracepoint and specify a size
> as a filter to only see those that are really interesting. I haven't
> checked your slabinfo yet - hope to get to it later today.
The largest contributors seem to be
$ zcat slabinfo.txt.gz | awk '{printf "%s %d\n" , $1, $6*$15}' | head_and_tail.sh 133 | paste-with-diff.sh | sort -n -k3
initial diff [#pages]
radix_tree_node 3444 2592
debug_objects_cache 388 46159
file_lock_ctx 114 138570
buffer_head 5616 238704
kmalloc-256 328 573164
bio-3 24 1118984
So it seems we are accumulating bios and 256B objects. Buffer heads as
well but so much. Having over 4G worth of bios sounds really suspicious.
Note that they pin pages to be written so this might be consuming the
rest of the unaccounted memory! So the main question is why those bios
do not get dispatched or finished.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-07-13 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 8:27 Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) Matthias Dahl
2016-07-12 9:50 ` Michal Hocko
2016-07-12 11:28 ` Matthias Dahl
2016-07-12 11:49 ` Michal Hocko
2016-07-12 11:59 ` Michal Hocko
2016-07-12 12:42 ` Matthias Dahl
2016-07-12 14:07 ` Michal Hocko
2016-07-12 14:56 ` Matthias Dahl
2016-07-13 11:21 ` Michal Hocko
2016-07-13 12:18 ` Michal Hocko [this message]
2016-07-13 13:18 ` Matthias Dahl
2016-07-13 13:47 ` Michal Hocko
2016-07-13 15:32 ` Matthias Dahl
2016-07-13 16:24 ` [dm-devel] " Ondrej Kozina
2016-07-13 18:24 ` Matthias Dahl
2016-07-14 11:18 ` Tetsuo Handa
2016-07-15 7:11 ` Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) with check/repair/sync Matthias Dahl
2016-07-18 7:24 ` Matthias Dahl
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=20160713121828.GI28723@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=ml_linux-kernel@binary-island.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).