From: Alex Bligh <alex@alex.org.uk>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-kernel@vger.kernel.org, Alex Bligh <alex@alex.org.uk>
Subject: Re: Local DoS through write heavy I/O on CFQ & Deadline
Date: Fri, 12 Oct 2012 15:48:34 +0100 [thread overview]
Message-ID: <E6EF14955C67D6CA58918872@nimrod.local> (raw)
In-Reply-To: <20121012133044.GA10115@dhcp22.suse.cz>
--On 12 October 2012 15:30:45 +0200 Michal Hocko <mhocko@suse.cz> wrote:
>> Full info, including logs and scripts can be found at:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064521
>
> You seem to have 8G of RAM and dirty_ratio=20 resp.
> dirty_background_ratio=10 which means that 1.5G worth of dirty data
> until writer gets throttled which is a lot. Background writeback starts
> at 800M which is probably not sufficient as well. Have you tried to set
> dirty_bytes at a reasonable value (wrt. to your storage)?
This is for an appliance install where we have no idea how much
memory the box has in advance other than 'at least 4G' so it
is difficult to tune by default.
However, I don't think that would solve the problem as the zcat/dd
can always generate data faster than it can be written to disk unless
or until it is throttled, which it never is. Isn't the only thing that
is going to change that it ends up triggering the writeback earlier?
Happy to test etc - what would you suggest, dirty_ratio=5,
dirty_background_ratio=2 ?
--
Alex Bligh
next prev parent reply other threads:[~2012-10-12 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 12:23 Alex Bligh
2012-10-11 13:46 ` Alan Cox
2012-10-12 12:57 ` Alex Bligh
2012-10-12 13:30 ` Michal Hocko
2012-10-12 14:48 ` Alex Bligh [this message]
2012-10-12 14:58 ` Michal Hocko
2012-10-12 16:29 ` Alex Bligh
2012-10-13 13:53 ` Hillf Danton
2012-10-13 19:33 ` Alex Bligh
2012-10-14 2:43 ` Hillf Danton
2012-10-15 8:17 ` Michal Hocko
2012-10-18 21:28 ` Jan Kara
2012-10-18 22:13 ` Chris Friesen
2012-10-18 22:24 ` Jan Kara
2012-10-14 21:17 ` Dave Chinner
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=E6EF14955C67D6CA58918872@nimrod.local \
--to=alex@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
/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®