From: tytso@mit.edu (Theodore Ts'o)
Subject: [TUHS] signals and blocked in I/O
Date: Sat, 2 Dec 2017 09:59:52 -0500 [thread overview]
Message-ID: <20171202145952.m4v76unuz5vbw4e5@thunk.org> (raw)
In-Reply-To: <20171201230934.GA24335@mcvoy.com>
On Fri, Dec 01, 2017 at 03:09:34PM -0800, Larry McVoy wrote:
>
> It's the old "10 pounds of shit in a 5 pound bag" problem, same old stuff,
> just a bigger bag.
>
> The problem is that OOM can't kill the processes that are the problem,
> they are stuck in disk wait. That's why I started asking why can't you
> kill a process that's in the middle of I/O.
You may need to solve the problem much earlier, by write throttling
the process which is generating so many dirty pages in the first
place. At one point Linux would press-gang the badly behaved process
which was generating lots of dirty pages into helping to deactivate
and clean pages; it doesn't do this any more, but stopping processes
which are being badly behaved until the writeback daemons can catch up
is certainly kinder than OOM-killing the bad process.
Are you using ZFS? It does have a write throttling knob, apparently.
- Ted
next prev parent reply other threads:[~2017-12-02 14:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 15:44 Larry McVoy
2017-12-01 15:53 ` Dan Cross
2017-12-01 16:11 ` Clem Cole
2017-12-01 16:18 ` Larry McVoy
2017-12-01 16:33 ` Warner Losh
2017-12-01 17:26 ` Larry McVoy
2017-12-01 19:10 ` Chris Torek
2017-12-01 23:21 ` Dave Horsfall
2017-12-01 21:33 ` Bakul Shah
2017-12-01 22:38 ` Larry McVoy
2017-12-01 23:03 ` Ralph Corderoy
2017-12-01 23:09 ` Larry McVoy
2017-12-01 23:42 ` Bakul Shah
2017-12-02 0:48 ` Larry McVoy
2017-12-02 1:40 ` Bakul Shah
2017-12-03 13:50 ` Ralph Corderoy
2017-12-04 16:36 ` arnold
2017-12-04 16:58 ` Arthur Krewat
2017-12-04 17:19 ` Warner Losh
2017-12-05 2:12 ` Bakul Shah
2017-12-04 22:07 ` Dave Horsfall
2017-12-04 22:54 ` Ron Natalie
2017-12-04 22:56 ` Warner Losh
2017-12-05 0:49 ` Dave Horsfall
2017-12-05 0:58 ` Arthur Krewat
2017-12-05 2:15 ` Dave Horsfall
2017-12-05 2:54 ` Clem cole
2017-12-02 14:59 ` Theodore Ts'o [this message]
2017-12-01 16:01 ` Dave Horsfall
2017-12-01 16:24 ` Warner Losh
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=20171202145952.m4v76unuz5vbw4e5@thunk.org \
--to=tytso@mit.edu \
/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).