From: Matthias Dahl <ml_linux-kernel@binary-island.eu>
To: Michal Hocko <mhocko@kernel.org>
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: Tue, 12 Jul 2016 16:56:32 +0200 [thread overview]
Message-ID: <459d501038de4d25db6d140ac5ea5f8d@mail.ud19.udmedia.de> (raw)
In-Reply-To: <20160712140715.GL14586@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
Hello Michal...
On 2016-07-12 16:07, Michal Hocko wrote:
> /proc/slabinfo could at least point on who is eating that memory.
Thanks. I have made another test (and thus again put the RAID10 out of
sync for the 100th time, sigh) and made regular snapshots of slabinfo
which I have attached to this mail.
> Direct IO doesn't get throttled like buffered IO.
Is buffered i/o not used in both cases if I don't explicitly request
direct i/o?
dd if=/dev/zero /dev/md126p5 bs=512K
and dd if=/dev/zero /dev/mapper/test-device bs=512K
Given that the test-device is dm-crypt on md125p5. Aren't both using
buffered i/o?
> the number of pages under writeback was more or less same throughout
> the time but there are some local fluctuations when some pages do get
> completed.
The pages under writeback are those directly destined for the disk, so
after dm-crypt had done its encryption?
> If not you can enable allocator trace point for a particular object
> size (or range of sizes) and see who is requesting them.
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.
Thanks,
Matthias
--
Dipl.-Inf. (FH) Matthias Dahl | Software Engineer | binary-island.eu
services: custom software [desktop, mobile, web], server administration
[-- Attachment #2: slabinfo.txt.gz --]
[-- Type: application/x-gzip, Size: 30968 bytes --]
next prev parent reply other threads:[~2016-07-12 14:56 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 [this message]
2016-07-13 11:21 ` Michal Hocko
2016-07-13 12:18 ` Michal Hocko
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=459d501038de4d25db6d140ac5ea5f8d@mail.ud19.udmedia.de \
--to=ml_linux-kernel@binary-island.eu \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=mhocko@kernel.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 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).