From: Mike Galbraith <efault@gmx.de>
To: Mike Mestnik <cheako@mikemestnik.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Chronic resource starvation.
Date: Mon, 16 Jan 2012 07:07:56 +0100 [thread overview]
Message-ID: <1326694076.6446.166.camel@marge.simson.net> (raw)
In-Reply-To: <4F13B902.1090503@mikemestnik.net>
On Sun, 2012-01-15 at 23:43 -0600, Mike Mestnik wrote:
> Does fdatasync still cause this problem? I'm sure there must be
> some way to 'group' applications together that should be allowed to
> avoid this effect and even insert IO requests during the operation if
> given a high enough priority.
And btw, that resource prioritization exists now for both CPU and IO
resources, look into cgroups and ionice for non-cgroup IO. For the CPU
scheduler, you can automate task grouping by enabling SCHED_AUTOGROUP,
and some distros use a userland automation solution via systemd. I
don't know if systemd does IO group automation, but groups won't help
defective spinning media anyway.
-Mike
prev parent reply other threads:[~2012-01-16 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 3:17 Chronic resource starvation Mike Mestnik
2012-01-14 20:21 ` Mike Mestnik
2012-01-15 12:08 ` Mike Galbraith
2012-01-15 19:01 ` Mike Mestnik
2012-01-16 2:39 ` Mike Galbraith
2012-01-16 5:43 ` Mike Mestnik
2012-01-16 5:51 ` Mike Galbraith
2012-01-16 6:07 ` Mike Galbraith [this message]
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=1326694076.6446.166.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=cheako@mikemestnik.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.