From: Michal Hocko <mhocko@suse.cz>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Huang Ying <ying.huang@intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Dave Chinner <david@fromorbit.com>, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [patch 07/12] mm: page_alloc: inline should_alloc_retry()
Date: Thu, 26 Mar 2015 15:11:28 +0100 [thread overview]
Message-ID: <20150326141128.GL15257@dhcp22.suse.cz> (raw)
In-Reply-To: <1427264236-17249-8-git-send-email-hannes@cmpxchg.org>
On Wed 25-03-15 02:17:11, Johannes Weiner wrote:
> The should_alloc_retry() function was meant to encapsulate retry
> conditions of the allocator slowpath, but there are still checks
> remaining in the main function, and much of how the retrying is
> performed also depends on the OOM killer progress. The physical
> separation of those conditions make the code hard to follow.
>
> Inline the should_alloc_retry() checks. Notes:
>
> - The __GFP_NOFAIL check is already done in __alloc_pages_may_oom(),
> replace it with looping on OOM killer progress
>
> - The pm_suspended_storage() check is meant to skip the OOM killer
> when reclaim has no IO available, move to __alloc_pages_may_oom()
>
> - The order < PAGE_ALLOC_COSTLY order is re-united with its original
> counterpart of checking whether reclaim actually made any progress
it should be order <= PAGE_ALLOC_COSTLY
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
The resulting code looks much better and logical.
After the COSTLY check is fixed.
Acked-by: Michal Hocko <mhocko@suse.cz>
> ---
> mm/page_alloc.c | 104 +++++++++++++++++---------------------------------------
> 1 file changed, 32 insertions(+), 72 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 9ebc760187ac..c1224ba45548 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -2329,48 +2329,6 @@ void warn_alloc_failed(gfp_t gfp_mask, int order, const char *fmt, ...)
> show_mem(filter);
> }
>
> -static inline int
> -should_alloc_retry(gfp_t gfp_mask, unsigned int order,
> - unsigned long did_some_progress,
> - unsigned long pages_reclaimed)
> -{
> - /* Do not loop if specifically requested */
> - if (gfp_mask & __GFP_NORETRY)
> - return 0;
> -
> - /* Always retry if specifically requested */
> - if (gfp_mask & __GFP_NOFAIL)
> - return 1;
> -
> - /*
> - * Suspend converts GFP_KERNEL to __GFP_WAIT which can prevent reclaim
> - * making forward progress without invoking OOM. Suspend also disables
> - * storage devices so kswapd will not help. Bail if we are suspending.
> - */
> - if (!did_some_progress && pm_suspended_storage())
> - return 0;
> -
> - /*
> - * In this implementation, order <= PAGE_ALLOC_COSTLY_ORDER
> - * means __GFP_NOFAIL, but that may not be true in other
> - * implementations.
> - */
> - if (order <= PAGE_ALLOC_COSTLY_ORDER)
> - return 1;
> -
> - /*
> - * For order > PAGE_ALLOC_COSTLY_ORDER, if __GFP_REPEAT is
> - * specified, then we retry until we no longer reclaim any pages
> - * (above), or we've reclaimed an order of pages at least as
> - * large as the allocation's order. In both cases, if the
> - * allocation still fails, we stop retrying.
> - */
> - if (gfp_mask & __GFP_REPEAT && pages_reclaimed < (1 << order))
> - return 1;
> -
> - return 0;
> -}
> -
> static inline struct page *
> __alloc_pages_may_oom(gfp_t gfp_mask, unsigned int order,
> const struct alloc_context *ac, unsigned long *did_some_progress)
> @@ -2409,16 +2367,18 @@ __alloc_pages_may_oom(gfp_t gfp_mask, unsigned int order,
> /* The OOM killer does not needlessly kill tasks for lowmem */
> if (ac->high_zoneidx < ZONE_NORMAL)
> goto out;
> - /* The OOM killer does not compensate for light reclaim */
> + /* The OOM killer does not compensate for IO-less reclaim */
> if (!(gfp_mask & __GFP_FS)) {
> /*
> * XXX: Page reclaim didn't yield anything,
> * and the OOM killer can't be invoked, but
> - * keep looping as per should_alloc_retry().
> + * keep looping as per tradition.
> */
> *did_some_progress = 1;
> goto out;
> }
> + if (pm_suspended_storage())
> + goto out;
> /* The OOM killer may not free memory on a specific node */
> if (gfp_mask & __GFP_THISNODE)
> goto out;
> @@ -2801,40 +2761,40 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
> if (page)
> goto got_pg;
>
> - /* Check if we should retry the allocation */
> + /* Do not loop if specifically requested */
> + if (gfp_mask & __GFP_NORETRY)
> + goto noretry;
> +
> + /* Keep reclaiming pages as long as there is reasonable progress */
> pages_reclaimed += did_some_progress;
> - if (should_alloc_retry(gfp_mask, order, did_some_progress,
> - pages_reclaimed)) {
> - /*
> - * If we fail to make progress by freeing individual
> - * pages, but the allocation wants us to keep going,
> - * start OOM killing tasks.
> - */
> - if (!did_some_progress) {
> - page = __alloc_pages_may_oom(gfp_mask, order, ac,
> - &did_some_progress);
> - if (page)
> - goto got_pg;
> - if (!did_some_progress)
> - goto nopage;
> - }
> + if ((did_some_progress && order < PAGE_ALLOC_COSTLY_ORDER) ||
> + ((gfp_mask & __GFP_REPEAT) && pages_reclaimed < (1 << order))) {
> /* Wait for some write requests to complete then retry */
> wait_iff_congested(ac->preferred_zone, BLK_RW_ASYNC, HZ/50);
> goto retry;
> - } else {
> - /*
> - * High-order allocations do not necessarily loop after
> - * direct reclaim and reclaim/compaction depends on compaction
> - * being called after reclaim so call directly if necessary
> - */
> - page = __alloc_pages_direct_compact(gfp_mask, order,
> - alloc_flags, ac, migration_mode,
> - &contended_compaction,
> - &deferred_compaction);
> - if (page)
> - goto got_pg;
> }
>
> + /* Reclaim has failed us, start killing things */
> + page = __alloc_pages_may_oom(gfp_mask, order, ac, &did_some_progress);
> + if (page)
> + goto got_pg;
> +
> + /* Retry as long as the OOM killer is making progress */
> + if (did_some_progress)
> + goto retry;
> +
> +noretry:
> + /*
> + * High-order allocations do not necessarily loop after
> + * direct reclaim and reclaim/compaction depends on compaction
> + * being called after reclaim so call directly if necessary
> + */
> + page = __alloc_pages_direct_compact(gfp_mask, order, alloc_flags,
> + ac, migration_mode,
> + &contended_compaction,
> + &deferred_compaction);
> + if (page)
> + goto got_pg;
> nopage:
> warn_alloc_failed(gfp_mask, order, NULL);
> got_pg:
> --
> 2.3.3
>
--
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>
next prev parent reply other threads:[~2015-03-26 14:11 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 6:17 [patch 00/12] mm: page_alloc: improve OOM mechanism and policy Johannes Weiner
2015-03-25 6:17 ` [patch 01/12] mm: oom_kill: remove unnecessary locking in oom_enable() Johannes Weiner
2015-03-26 0:51 ` David Rientjes
2015-03-26 11:51 ` Michal Hocko
2015-03-26 13:18 ` Michal Hocko
2015-03-26 19:30 ` David Rientjes
2015-03-26 11:43 ` Michal Hocko
2015-03-26 20:05 ` David Rientjes
2015-03-25 6:17 ` [patch 02/12] mm: oom_kill: clean up victim marking and exiting interfaces Johannes Weiner
2015-03-26 3:34 ` David Rientjes
2015-03-26 11:54 ` Michal Hocko
2015-03-25 6:17 ` [patch 03/12] mm: oom_kill: switch test-and-clear of known TIF_MEMDIE to clear Johannes Weiner
2015-03-26 3:31 ` David Rientjes
2015-03-26 11:05 ` Johannes Weiner
2015-03-26 19:50 ` David Rientjes
2015-03-30 14:48 ` Michal Hocko
2015-04-02 23:01 ` [patch] android, lmk: avoid setting TIF_MEMDIE if process has already exited David Rientjes
2015-04-28 22:50 ` [patch resend] " David Rientjes
2015-03-26 11:57 ` [patch 03/12] mm: oom_kill: switch test-and-clear of known TIF_MEMDIE to clear Michal Hocko
2015-03-25 6:17 ` [patch 04/12] mm: oom_kill: remove unnecessary locking in exit_oom_victim() Johannes Weiner
2015-03-26 12:53 ` Michal Hocko
2015-03-26 13:01 ` Michal Hocko
2015-03-26 15:10 ` Johannes Weiner
2015-03-26 15:04 ` Johannes Weiner
2015-03-25 6:17 ` [patch 05/12] mm: oom_kill: generalize OOM progress waitqueue Johannes Weiner
2015-03-26 13:03 ` Michal Hocko
2015-03-25 6:17 ` [patch 06/12] mm: oom_kill: simplify OOM killer locking Johannes Weiner
2015-03-26 13:31 ` Michal Hocko
2015-03-26 15:17 ` Johannes Weiner
2015-03-26 16:07 ` Michal Hocko
2015-03-25 6:17 ` [patch 07/12] mm: page_alloc: inline should_alloc_retry() Johannes Weiner
2015-03-26 14:11 ` Michal Hocko [this message]
2015-03-26 15:18 ` Johannes Weiner
2015-03-25 6:17 ` [patch 08/12] mm: page_alloc: wait for OOM killer progress before retrying Johannes Weiner
2015-03-25 14:15 ` Tetsuo Handa
2015-03-25 17:01 ` Vlastimil Babka
2015-03-26 11:28 ` Johannes Weiner
2015-03-26 11:24 ` Johannes Weiner
2015-03-26 14:32 ` Michal Hocko
2015-03-26 15:23 ` Johannes Weiner
2015-03-26 15:38 ` Michal Hocko
2015-03-26 18:17 ` Johannes Weiner
2015-03-27 14:01 ` [patch 08/12] mm: page_alloc: wait for OOM killer progressbefore retrying Tetsuo Handa
2015-03-26 15:58 ` [patch 08/12] mm: page_alloc: wait for OOM killer progress before retrying Michal Hocko
2015-03-26 18:23 ` Johannes Weiner
2015-03-25 6:17 ` [patch 09/12] mm: page_alloc: private memory reserves for OOM-killing allocations Johannes Weiner
2015-04-14 16:49 ` Michal Hocko
2015-04-24 19:13 ` Johannes Weiner
2015-03-25 6:17 ` [patch 10/12] mm: page_alloc: emergency reserve access for __GFP_NOFAIL allocations Johannes Weiner
2015-04-14 16:55 ` Michal Hocko
2015-03-25 6:17 ` [patch 11/12] mm: page_alloc: do not lock up GFP_NOFS allocations upon OOM Johannes Weiner
2015-03-26 14:50 ` Michal Hocko
2015-03-25 6:17 ` [patch 12/12] mm: page_alloc: do not lock up low-order " Johannes Weiner
2015-03-26 15:32 ` Michal Hocko
2015-03-26 19:58 ` [patch 00/12] mm: page_alloc: improve OOM mechanism and policy Dave Chinner
2015-03-27 15:05 ` Johannes Weiner
2015-03-30 0:32 ` Dave Chinner
2015-03-30 19:31 ` Johannes Weiner
2015-04-01 15:19 ` Michal Hocko
2015-04-01 21:39 ` Dave Chinner
2015-04-02 7:29 ` Michal Hocko
2015-04-07 14:18 ` Johannes Weiner
2015-04-11 7:29 ` Tetsuo Handa
2015-04-13 12:49 ` Michal Hocko
2015-04-13 12:46 ` Michal Hocko
2015-04-14 0:11 ` Dave Chinner
2015-04-14 7:20 ` Michal Hocko
2015-04-14 10:36 ` Johannes Weiner
2015-04-14 14:23 ` 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=20150326141128.GL15257@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=ying.huang@intel.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