From: Michal Hocko <mhocko@kernel.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] mm:vmscan: clean up classzone_idx
Date: Mon, 4 Apr 2016 11:42:59 +0200 [thread overview]
Message-ID: <20160404094259.GC13463@dhcp22.suse.cz> (raw)
In-Reply-To: <1459727185-5753-1-git-send-email-minchan@kernel.org>
On Mon 04-04-16 08:46:25, Minchan Kim wrote:
> [1] removed classzone_idx so we don't need code related to it.
> This patch cleans it up.
>
> [1] mm, oom: rework oom detection
As per http://lkml.kernel.org/r/20160404094213.GB13463@dhcp22.suse.cz
the removal of classzone_idx was unintentional and wrong.
>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@suse.com>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
> ---
> mm/vmscan.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index d84efa03c8a8..6e67de2a61ed 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -2551,16 +2551,8 @@ static void shrink_zones(struct zonelist *zonelist, struct scan_control *sc)
>
> for_each_zone_zonelist_nodemask(zone, z, zonelist,
> gfp_zone(sc->gfp_mask), sc->nodemask) {
> - enum zone_type classzone_idx;
> -
> if (!populated_zone(zone))
> continue;
> -
> - classzone_idx = requested_highidx;
> - while (!populated_zone(zone->zone_pgdat->node_zones +
> - classzone_idx))
> - classzone_idx--;
> -
> /*
> * Take care memory controller reclaiming has small influence
> * to global LRU.
> --
> 1.9.1
>
--
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-04-04 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 23:46 Minchan Kim
2016-04-04 9:42 ` 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=20160404094259.GC13463@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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