From: Alex Bligh <alex@alex.org.uk>
To: Hillf Danton <dhillf@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Alex Bligh <alex@alex.org.uk>
Subject: Re: Local DoS through write heavy I/O on CFQ & Deadline
Date: Sat, 13 Oct 2012 20:33:27 +0100 [thread overview]
Message-ID: <97166AE58C26A44D45569412@nimrod.local> (raw)
In-Reply-To: <CAJd=RBAdpGpSrx9e28MLmPAEhqRsCQGHNuc-sjUQPMTLO9agpQ@mail.gmail.com>
--On 13 October 2012 21:53:09 +0800 Hillf Danton <dhillf@gmail.com> wrote:
> Take a look at the "wait for writeback" problem please.
>
> Linux 3.0+ Disk performance problem - wrong pdflush behaviour
> https://lkml.org/lkml/2012/10/10/412
I'm guessing that's related but may not be the whole story. My
test case is rather simpler, and Viktor says that with the
patch causing his regression reverted, "After I've set the dirty_bytes
over the file size the writes are never blocked.". That suggests
to me that in order to avoid write blocking he needs dirty_bytes
larger than the file size. As the bytes written in my test case
exceed RAM, that's going to be be an issue as dirty_bytes is always
going to be hit; I think it Viktor's case he is trying to avoid
it being hit at all.
Or perhaps I have the wrong end of the stick.
--
Alex Bligh
next prev parent reply other threads:[~2012-10-13 19:33 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
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 [this message]
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=97166AE58C26A44D45569412@nimrod.local \
--to=alex@alex.org.uk \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®