From: Matthias Dahl <ml_linux-kernel@binary-island.eu>
To: Mike Snitzer <snitzer@redhat.com>
Cc: linux-mm@kvack.org, dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] [4.7.0rc6] Page Allocation Failures with dm-crypt
Date: Mon, 11 Jul 2016 16:47:17 +0200 [thread overview]
Message-ID: <2786d2f951a90eb00502096aca71e05b@mail.ud19.udmedia.de> (raw)
In-Reply-To: <20160711133051.GA28308@redhat.com>
Hello Mike...
On 2016-07-11 15:30, Mike Snitzer wrote:
> But that is expected given you're doing an unbounded buffered write to
> the device. What isn't expected, to me anyway, is that the mm
> subsystem
> (or the default knobs for buffered writeback) would be so aggressive
> about delaying writeback.
Ok. But, and please correct me if I am wrong, I was under the impression
that only the file caches/buffers were affected, iow, if I use free to
monitor the memory usage, the used memory increases to the point where
it
consumes all memory, not the buffers/file caches... that is what I am
seeing here.
Also, if I use dd directly on the device w/o dm-crypt in-between, there
is no problem. Sure, buffers increase hugely also... but only those.
> Why are you doing this test anyway? Such a large buffered write
> doesn't
> seem to accurately model any application I'm aware of (but obviously it
> should still "work").
It is not a test per se. I simply wanted to fill the partition with
noise.
And doing it this way is faster than using urandom or anything. ;-) That
is
why I stumbled over this issue in the first place.
> Now that is weird. Are you (or the distro you're using) setting any mm
> subsystem tunables to really broken values?
You can see those in my initial mail. I attached the kernel warnings,
all
sysctl tunables and more. Maybe that helps.
> What is your raid10's full stripesize?
4 disks in RAID10, with a stripe size of 64k.
> Is your dd IO size of 512K somehow triggering excess R-M-W cycles which
> is exacerbating the problem?
The partitions are properly aligned. And as you can see, with that
stripe
size, there is no issue.
In the meantime I did some further tests: I created an ext2 on the
partition as well as a 60GiB container image on it. I used that image
with dm-crypt, same parameters as before. No matter what I do here, I
cannot trigger the same behavior.
Maybe it is an interaction issue between dm-crypt and the s/w RAID. But
at this point, I have no idea how to further diagnose/test it. If you
can point me in any direction that would be great...
With Kind Regards from Germany
Matthias
--
Dipl.-Inf. (FH) Matthias Dahl | Software Engineer | binary-island.eu
services: custom software [desktop, mobile, web], server administration
next prev parent reply other threads:[~2016-07-11 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 13:40 Matthias Dahl
2016-07-11 8:31 ` Matthias Dahl
2016-07-11 13:18 ` Mike Snitzer
2016-07-11 13:27 ` [dm-devel] " Matthias Dahl
2016-07-11 13:44 ` Mike Snitzer
2016-07-11 13:30 ` Mike Snitzer
2016-07-11 14:47 ` Matthias Dahl [this message]
2016-07-12 8:06 ` [dm-devel] " 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=2786d2f951a90eb00502096aca71e05b@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=snitzer@redhat.com \
/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
all inboxes | Powered by JetHome®