From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: vbabka@suse.cz, iamjoonsoo.kim@lge.com,
mgorman@techsingularity.net, riel@redhat.com,
rientjes@google.com, 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 14:14:18 -0700 [thread overview]
Message-ID: <20160824141418.b266d5a0bddf9170181f8627@linux-foundation.org> (raw)
In-Reply-To: <20160824070859.GC31179@dhcp22.suse.cz>
On Wed, 24 Aug 2016 09:08:59 +0200 Michal Hocko <mhocko@kernel.org> wrote:
> 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.
Yes. And I think we're still waiting testing feedback from the
reporters on
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?
I suppose so. We can leave
mm-oom-prevent-pre-mature-oom-killer-invocation-for-high-order-request.patch
in place in mainline for 4.8 so it can be respectably backported into
-stable.
And we may as well fold
mm-compaction-more-reliably-increase-direct-compaction-priority.patch
into the patch which re-adds should_compact_retry()?
--
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:[~2016-08-24 21:14 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
2016-08-24 21:14 ` Andrew Morton [this message]
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=20160824141418.b266d5a0bddf9170181f8627@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@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