linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Minchan Kim <minchan@kernel.org>,
	Hillf Danton <hillf.zj@alibaba-inc.com>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] follow up nodereclaim for 32b fix
Date: Tue, 17 Jan 2017 11:13:16 +0000	[thread overview]
Message-ID: <20170117111316.6eakdx7ow6yodtf2@suse.de> (raw)
In-Reply-To: <20170117103702.28542-1-mhocko@kernel.org>

On Tue, Jan 17, 2017 at 11:36:59AM +0100, Michal Hocko wrote:
> Hi,
> I have previously posted this as an RFC [1] but there didn't seem to be
> any objections other than some requests to reorganize the changes in
> a slightly different way so I am reposting the series and asking for
> inclusion.
> 
> This is a follow up on top of [2]. The patch 1 cleans up the code a bit.
> I haven't seen any real issues or bug reports but conceptualy ignoring
> the maximum eligible zone in get_scan_count is wrong by definition. This
> is what patch 2 does.  Patch 3 removes inactive_reclaimable_pages
> which was a kind of hack around for the problem which should have been
> addressed at get_scan_count.
> 
> There is one more place which needs a special handling which is not
> a part of this series. too_many_isolated can get confused as well. I
> already have some preliminary work but it still needs some testing so I
> will post it separatelly.
> 
> Michal Hocko (3):
>       mm, vmscan: cleanup lru size claculations
>       mm, vmscan: consider eligible zones in get_scan_count
>       Revert "mm: bail out in shrink_inactive_list()"
> 

Acked-by: Mel Gorman <mgorman@suse.de>

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

      parent reply	other threads:[~2017-01-17 11:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 10:36 Michal Hocko
2017-01-17 10:37 ` [PATCH 1/3] mm, vmscan: cleanup lru size claculations Michal Hocko
2017-01-17 10:37 ` [PATCH 2/3] mm, vmscan: consider eligible zones in get_scan_count Michal Hocko
2017-01-18 16:46   ` Johannes Weiner
2017-02-06  8:10   ` Michal Hocko
2017-02-06 23:40     ` Andrew Morton
2017-01-17 10:37 ` [PATCH 3/3] Revert "mm: bail out in shrink_inactive_list()" Michal Hocko
2017-01-18 16:48   ` Johannes Weiner
2017-01-17 11:13 ` Mel Gorman [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=20170117111316.6eakdx7ow6yodtf2@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=hillf.zj@alibaba-inc.com \
    --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