From: Michal Hocko <mhocko@kernel.org>
To: Raymond Jennings <shentino@gmail.com>
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: Mon, 17 Apr 2017 10:19:47 +0200 [thread overview]
Message-ID: <20170417081946.GB12511@dhcp22.suse.cz> (raw)
In-Reply-To: <CAGDaZ_r+HsMnrdW-i2PtZeCUwJnKs9D_DO-fosCo7TexLWDkNw@mail.gmail.com>
On Thu 13-04-17 11:13:41, Raymond Jennings wrote:
> 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.
How have you checked that?
> Are you guys suggesting that if dirty memory gets high enough the
> writeback turns into an OOM dodger that preempts foreground I/O?
Once you exceed the dirty limit, writers starts being throttled on new
writes. If things go especially bad than all writers get throttled
basically and that is where your stalls come from most probably.
> What I was hoping for is for dirty writeback itself to be throttled
> and stay out of the way of foreground I/O.
The amount of dirty data would just grow without any bounds if the
writers were not throttled...
--
Michal Hocko
SUSE Labs
--
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>
prev parent reply other threads:[~2017-04-17 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 17:39 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
2017-04-17 8:19 ` Michal Hocko [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=20170417081946.GB12511@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=shentino@gmail.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