From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Minchan Kim <minchan@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] mm: vmscan: reclaim highmem zone if buffer_heads is over limit
Date: Fri, 1 Apr 2016 13:14:58 -0700 [thread overview]
Message-ID: <20160401131458.e31d45f56a98c62669b35e3d@linux-foundation.org> (raw)
In-Reply-To: <20160401080350.GB8916@dhcp22.suse.cz>
On Fri, 1 Apr 2016 10:03:50 +0200 Michal Hocko <mhocko@kernel.org> wrote:
> On Fri 01-04-16 17:00:58, Minchan Kim wrote:
> [...]
> > [2] commit 5acbd3bfc93b ("mm, oom: rework oom detection")
>
> I didn't look a tht patch yet but wanted to note that this sha is most
> probably from linux-next and won't be stable. Also this patch will most
> likely see some changes in future so making changes on top which should
> go in independetly will likely just complicate things.
Yes, we'll need two patches please. One to fix 6b4f7799c6a5 ("mm:
vmscan: invoke slab shrinkers from shrink_zone()") (which is in
mainline) and a second to clean up -mm's "mm, oom: rework oom detection".
--
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-04-01 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 8:00 [PATCH] mm: vmscan: reclaim highmem zone if buffer_heads is over limit Minchan Kim
2016-04-01 8:03 ` Michal Hocko
2016-04-01 20:14 ` Andrew Morton [this message]
2016-04-03 23:49 ` Minchan Kim
-- strict thread matches above, loose matches on Subject: below --
2016-04-03 23:46 Minchan Kim
2016-04-05 20:37 ` Andrew Morton
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=20160401131458.e31d45f56a98c62669b35e3d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.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).