From: Michal Hocko <mhocko@kernel.org>
To: Hillf Danton <hillf.zj@alibaba-inc.com>
Cc: linux-mm@kvack.org, "'Andrew Morton'" <akpm@linux-foundation.org>,
"'Linus Torvalds'" <torvalds@linux-foundation.org>,
"'Mel Gorman'" <mgorman@suse.de>,
"'Johannes Weiner'" <hannes@cmpxchg.org>,
"'Rik van Riel'" <riel@redhat.com>,
"'David Rientjes'" <rientjes@google.com>,
"'Tetsuo Handa'" <penguin-kernel@I-love.SAKURA.ne.jp>,
"'LKML'" <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [RFC 2/3] mm: throttle on IO only when there are too many dirty and writeback pages
Date: Fri, 30 Oct 2015 09:37:09 +0100 [thread overview]
Message-ID: <20151030083709.GD18429@dhcp22.suse.cz> (raw)
In-Reply-To: <00f301d112ca$14db86c0$3e929440$@alibaba-inc.com>
On Fri 30-10-15 12:18:50, Hillf Danton wrote:
>
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -3191,8 +3191,23 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
> > */
> > if (__zone_watermark_ok(zone, order, min_wmark_pages(zone),
> > ac->high_zoneidx, alloc_flags, target)) {
> > - /* Wait for some write requests to complete then retry */
> > - wait_iff_congested(zone, BLK_RW_ASYNC, HZ/50);
> > + unsigned long writeback = zone_page_state(zone, NR_WRITEBACK),
> > + dirty = zone_page_state(zone, NR_FILE_DIRTY);
> > +
> > + if (did_some_progress)
> > + goto retry;
> > +
> > + /*
> > + * If we didn't make any progress and have a lot of
> > + * dirty + writeback pages then we should wait for
> > + * an IO to complete to slow down the reclaim and
> > + * prevent from pre mature OOM
> > + */
> > + if (2*(writeback + dirty) > reclaimable)
> > + congestion_wait(BLK_RW_ASYNC, HZ/10);
> > + else
> > + cond_resched();
> > +
>
> Looks the vmstat updater issue is not addressed.
This is not the aim of this patch set.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2015-10-30 8:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:17 RFC: OOM detection rework v1 mhocko
2015-10-29 15:17 ` [RFC 1/3] mm, oom: refactor oom detection mhocko
2015-10-30 4:10 ` Hillf Danton
2015-10-30 8:36 ` Michal Hocko
2015-10-30 10:14 ` Michal Hocko
2015-10-30 13:32 ` Tetsuo Handa
2015-10-30 14:55 ` Michal Hocko
2015-10-31 3:57 ` Hillf Danton
2015-10-30 5:23 ` Kamezawa Hiroyuki
2015-10-30 8:23 ` Michal Hocko
2015-10-30 9:41 ` Kamezawa Hiroyuki
2015-10-30 10:18 ` Michal Hocko
2015-11-12 12:39 ` Michal Hocko
2015-10-29 15:17 ` [RFC 2/3] mm: throttle on IO only when there are too many dirty and writeback pages mhocko
2015-10-30 4:18 ` Hillf Danton
2015-10-30 8:37 ` Michal Hocko [this message]
2015-10-30 5:48 ` Kamezawa Hiroyuki
2015-10-30 8:38 ` Michal Hocko
2015-10-29 15:17 ` [RFC 3/3] mm: use watermak checks for __GFP_REPEAT high order allocations mhocko
2015-11-12 12:44 ` RFC: OOM detection rework v1 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=20151030083709.GD18429@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).