From: Hillf Danton <hdanton@sina.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hillf Danton <hdanton@sina.com>, Michal Hocko <mhocko@kernel.org>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrea Arcangeli <aarcange@redhat.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/3] mm, reclaim: make should_continue_reclaim performdryrun detection
Date: Mon, 5 Aug 2019 17:27:51 +0800 [thread overview]
Message-ID: <20190805092751.4976-1-hdanton@sina.com> (raw)
On Mon, 5 Aug 2019 16:43:04 +0800 Vlastimil Babka wrote:
>
> On 8/3/19 12:39 AM, Mike Kravetz wrote:
> > From: Hillf Danton <hdanton@sina.com>
> >
> > Address the issue of should_continue_reclaim continuing true too often
> > for __GFP_RETRY_MAYFAIL attempts when !nr_reclaimed and nr_scanned.
> > This could happen during hugetlb page allocation causing stalls for
> > minutes or hours.
> >
> > We can stop reclaiming pages if compaction reports it can make a progress.
> > A code reshuffle is needed to do that.
>
> > And it has side-effects, however,
> > with allocation latencies in other cases but that would come at the cost
> > of potential premature reclaim which has consequences of itself.
>
> Based on Mel's longer explanation, can we clarify the wording here? e.g.:
>
> There might be side-effect for other high-order allocations that would
> potentially benefit from more reclaim before compaction for them to be
> faster and less likely to stall, but the consequences of
> premature/over-reclaim are considered worse.
>
> > We can also bail out of reclaiming pages if we know that there are not
> > enough inactive lru pages left to satisfy the costly allocation.
> >
> > We can give up reclaiming pages too if we see dryrun occur, with the
> > certainty of plenty of inactive pages. IOW with dryrun detected, we are
> > sure we have reclaimed as many pages as we could.
> >
> > Cc: Mike Kravetz <mike.kravetz@oracle.com>
> > Cc: Mel Gorman <mgorman@suse.de>
> > Cc: Michal Hocko <mhocko@kernel.org>
> > Cc: Vlastimil Babka <vbabka@suse.cz>
> > Cc: Johannes Weiner <hannes@cmpxchg.org>
> > Signed-off-by: Hillf Danton <hdanton@sina.com>
> > Tested-by: Mike Kravetz <mike.kravetz@oracle.com>
> > Acked-by: Mel Gorman <mgorman@suse.de>
>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> I will send some followup cleanup.
>
> There should be also Mike's SOB?
Yes, definitely.
Thanks
Hillf
next reply other threads:[~2019-08-05 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 9:27 Hillf Danton [this message]
2019-08-05 13:13 ` Vlastimil Babka
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=20190805092751.4976-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.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