From: Raymond Jennings <shentino@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: Heavy I/O causing slow interactivity
Date: Thu, 13 Apr 2017 11:13:41 -0700 [thread overview]
Message-ID: <CAGDaZ_r+HsMnrdW-i2PtZeCUwJnKs9D_DO-fosCo7TexLWDkNw@mail.gmail.com> (raw)
In-Reply-To: <20170405184325.GV6035@dhcp22.suse.cz>
Would it make a difference if I cited that
My intent on upping the limits so high and pushing the dirty expiry so
far into the future was to *avoid* triggering background writeback.
In fact, dirty memory during one of these tests never actually rose a bunch.
Are you guys suggesting that if dirty memory gets high enough the
writeback turns into an OOM dodger that preempts foreground I/O?
What I was hoping for is for dirty writeback itself to be throttled
and stay out of the way of foreground I/O.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-04-13 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 17:39 Heavy I/O causing slow interactivity Raymond Jennings
2017-04-04 11:25 ` Michal Hocko
2017-04-05 12:53 ` Mike Rapoport
2017-04-05 18:15 ` Raymond Jennings
2017-04-05 18:43 ` Michal Hocko
2017-04-13 18:13 ` Raymond Jennings [this message]
2017-04-17 8:19 ` Michal Hocko
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=CAGDaZ_r+HsMnrdW-i2PtZeCUwJnKs9D_DO-fosCo7TexLWDkNw@mail.gmail.com \
--to=shentino@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rppt@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).