linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: akpm@linux-foundation.org
Cc: vbabka@suse.cz, iamjoonsoo.kim@lge.com,
	mgorman@techsingularity.net, riel@redhat.com,
	rientjes@google.com, mm-commits@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [wrecked] mm-compaction-more-reliably-increase-direct-compaction-priority.patch removed from -mm tree
Date: Wed, 24 Aug 2016 09:08:59 +0200	[thread overview]
Message-ID: <20160824070859.GC31179@dhcp22.suse.cz> (raw)
In-Reply-To: <57bcb948./5Xz5gcuIQjtLmuG%akpm@linux-foundation.org>

Hi Andrew,
I guess the reason this patch has been dropped is due to
mm-oom-prevent-pre-mature-oom-killer-invocation-for-high-order-request.patch.

I guess we will wait for the above patch to get to Linus, revert it in mmotm
and re-apply
mm-compaction-more-reliably-increase-direct-compaction-priority.patch
again, right?

On Tue 23-08-16 13:59:52, Andrew Morton wrote:
> 
> The patch titled
>      Subject: mm, compaction: more reliably increase direct compaction priority
> has been removed from the -mm tree.  Its filename was
>      mm-compaction-more-reliably-increase-direct-compaction-priority.patch
> 
> This patch was dropped because other changes were merged, which wrecked this patch
> 
> ------------------------------------------------------
> From: Vlastimil Babka <vbabka@suse.cz>
> Subject: mm, compaction: more reliably increase direct compaction priority
> 
> During reclaim/compaction loop, compaction priority can be increased by
> the should_compact_retry() function, but the current code is not optimal. 
> Priority is only increased when compaction_failed() is true, which means
> that compaction has scanned the whole zone.  This may not happen even
> after multiple attempts with a lower priority due to parallel activity, so
> we might needlessly struggle on the lower priorities and possibly run out
> of compaction retry attempts in the process.
> 
> After this patch we are guaranteed at least one attempt at the highest
> compaction priority even if we exhaust all retries at the lower
> priorities.
> 
> Link: http://lkml.kernel.org/r/20160810091226.6709-7-vbabka@suse.cz
> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Mel Gorman <mgorman@techsingularity.net>
> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Cc: David Rientjes <rientjes@google.com>
> Cc: Rik van Riel <riel@redhat.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  mm/page_alloc.c |   18 +++++++++++-------
>  1 file changed, 11 insertions(+), 7 deletions(-)
> 
> diff -puN mm/page_alloc.c~mm-compaction-more-reliably-increase-direct-compaction-priority mm/page_alloc.c
> --- a/mm/page_alloc.c~mm-compaction-more-reliably-increase-direct-compaction-priority
> +++ a/mm/page_alloc.c
> @@ -3153,13 +3153,8 @@ should_compact_retry(struct alloc_contex
>  	 * so it doesn't really make much sense to retry except when the
>  	 * failure could be caused by insufficient priority
>  	 */
> -	if (compaction_failed(compact_result)) {
> -		if (*compact_priority > MIN_COMPACT_PRIORITY) {
> -			(*compact_priority)--;
> -			return true;
> -		}
> -		return false;
> -	}
> +	if (compaction_failed(compact_result))
> +		goto check_priority;
>  
>  	/*
>  	 * make sure the compaction wasn't deferred or didn't bail out early
> @@ -3183,6 +3178,15 @@ should_compact_retry(struct alloc_contex
>  	if (compaction_retries <= max_retries)
>  		return true;
>  
> +	/*
> +	 * Make sure there is at least one attempt at the highest priority
> +	 * if we exhausted all retries at the lower priorities
> +	 */
> +check_priority:
> +	if (*compact_priority > MIN_COMPACT_PRIORITY) {
> +		(*compact_priority)--;
> +		return true;
> +	}
>  	return false;
>  }
>  #else
> _
> 
> Patches currently in -mm which might be from vbabka@suse.cz are
> 
> mm-compaction-make-whole_zone-flag-ignore-cached-scanner-positions.patch
> mm-compaction-cleanup-unused-functions.patch
> mm-compaction-rename-compact_partial-to-compact_success.patch
> mm-compaction-dont-recheck-watermarks-after-compact_success.patch
> mm-compaction-add-the-ultimate-direct-compaction-priority.patch
> mm-compaction-add-the-ultimate-direct-compaction-priority-fix.patch
> mm-compaction-use-correct-watermark-when-checking-compaction-success.patch
> mm-compaction-create-compact_gap-wrapper.patch
> mm-compaction-create-compact_gap-wrapper-fix.patch
> mm-compaction-use-proper-alloc_flags-in-__compaction_suitable.patch
> mm-compaction-require-only-min-watermarks-for-non-costly-orders.patch
> mm-compaction-require-only-min-watermarks-for-non-costly-orders-fix.patch
> mm-vmscan-make-compaction_ready-more-accurate-and-readable.patch

-- 
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>

       reply	other threads:[~2016-08-24  7:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57bcb948./5Xz5gcuIQjtLmuG%akpm@linux-foundation.org>
2016-08-24  7:08 ` Michal Hocko [this message]
2016-08-24 21:14   ` Andrew Morton
2016-08-25  7:36     ` 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=20160824070859.GC31179@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mm-commits@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=vbabka@suse.cz \
    /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