From: Michal Hocko <mhocko@suse.cz>
To: Andrew Morton <akpm@linux-foundation.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: Thu, 25 Aug 2016 09:36:47 +0200 [thread overview]
Message-ID: <20160825073646.GF4230@dhcp22.suse.cz> (raw)
In-Reply-To: <20160824141418.b266d5a0bddf9170181f8627@linux-foundation.org>
On Wed 24-08-16 14:14:18, Andrew Morton wrote:
> 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?
yes
> > 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()?
I am not sure combining those two into a single patch would be better.
It is true it would be bisect safe but those patches are not really
related because there are other changes for the compaction improvements
which already made a difference. This one is merely yet-another-change
on top. Let me think about that, though.
--
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:[~2016-08-25 7:36 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
2016-08-25 7:36 ` 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=20160825073646.GF4230@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--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