All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org, Mel Gorman <mgorman@suse.de>,
	Minchan Kim <minchan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH 1/2] mm, vmscan: consider eligible zones in get_scan_count
Date: Mon, 16 Jan 2017 10:29:56 +0100	[thread overview]
Message-ID: <20170116092956.GC13641@dhcp22.suse.cz> (raw)
In-Reply-To: <20170114161236.GB26139@cmpxchg.org>

On Sat 14-01-17 11:12:36, Johannes Weiner wrote:
> On Tue, Jan 10, 2017 at 01:55:51PM +0100, Michal Hocko wrote:
> > From: Michal Hocko <mhocko@suse.com>
> > 
> > get_scan_count considers the whole node LRU size when
> > - doing SCAN_FILE due to many page cache inactive pages
> > - calculating the number of pages to scan
> > 
> > in both cases this might lead to unexpected behavior especially on 32b
> > systems where we can expect lowmem memory pressure very often.
> 
> The amount of retrofitting zones back into reclaim is disappointing :/

Agreed
 
> >  /*
> > + * Return the number of pages on the given lru which are eligible for the
> > + * given zone_idx
> > + */
> > +static unsigned long lruvec_lru_size_eligibe_zones(struct lruvec *lruvec,
> > +		enum lru_list lru, int zone_idx)
> > +{
> > +	struct pglist_data *pgdat = lruvec_pgdat(lruvec);
> > +	unsigned long lru_size;
> > +	int zid;
> > +
> > +	lru_size = lruvec_lru_size(lruvec, lru);
> > +	for (zid = zone_idx + 1; zid < MAX_NR_ZONES; zid++) {
> > +		struct zone *zone = &pgdat->node_zones[zid];
> > +		unsigned long size;
> > +
> > +		if (!managed_zone(zone))
> > +			continue;
> > +
> > +		size = lruvec_zone_lru_size(lruvec, lru, zid);
> > +		lru_size -= min(size, lru_size);
> > +	}
> > +
> > +	return lru_size;
> 
> The only other use of lruvec_lru_size() is also in get_scan_count(),
> where it decays the LRU pressure balancing ratios. That caller wants
> to operate on the entire lruvec.
> 
> Can you instead add the filtering logic to lruvec_lru_size() directly,
> and pass MAX_NR_ZONES when operating on the entire lruvec? That would
> make the code quite a bit clearer than having 3 different lruvec size
> querying functions.

OK, fair point. What about this?
---

  reply	other threads:[~2017-01-16  9:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 12:55 [RFC PATCH 0/2] follow up nodereclaim for 32b fix Michal Hocko
2017-01-10 12:55 ` [RFC PATCH 1/2] mm, vmscan: consider eligible zones in get_scan_count Michal Hocko
2017-01-11  6:18   ` Hillf Danton
2017-01-13  9:18   ` Michal Hocko
2017-01-17  6:47     ` Minchan Kim
2017-01-14 16:12   ` Johannes Weiner
2017-01-16  9:29     ` Michal Hocko [this message]
2017-01-16 16:01       ` Johannes Weiner
2017-01-16 19:33         ` [PATCH 1/3] mm, vmscan: cleanup lru size claculations Michal Hocko
2017-01-16 19:33           ` Michal Hocko
2017-01-16 19:33           ` [PATCH 2/3] mm, vmscan: consider eligible zones in get_scan_count Michal Hocko
2017-01-16 19:33             ` Michal Hocko
2017-01-17  3:42             ` Hillf Danton
2017-01-17  3:42               ` Hillf Danton
2017-01-16 19:33           ` [PATCH 3/3] Reverted "mm: bail out in shrink_inactive_list()" Michal Hocko
2017-01-16 19:33             ` Michal Hocko
2017-01-17  3:58             ` Hillf Danton
2017-01-17  3:58               ` Hillf Danton
2017-01-17  6:58             ` Minchan Kim
2017-01-17  6:58               ` Minchan Kim
2017-01-17  3:40           ` [PATCH 1/3] mm, vmscan: cleanup lru size claculations Hillf Danton
2017-01-17  3:40             ` Hillf Danton
2017-01-17  6:58           ` Minchan Kim
2017-01-17  6:58             ` Minchan Kim
2017-01-10 12:55 ` [RFC PATCH 2/2] mm, vmscan: cleanup inactive_list_is_low Michal Hocko
2017-01-10 23:56   ` Minchan Kim
2017-01-11  6:22   ` Hillf Danton
2017-01-14 16:16   ` Johannes Weiner

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=20170116092956.GC13641@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.