[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7ea18bd9-d785-cc2c-7ca3-7a2e33002cfd@suse.cz>
Date: Tue, 8 Oct 2019 09:21:55 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Michal Hocko <mhocko@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: David Rientjes <rientjes@...gle.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Mel Gorman <mgorman@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH] mm, hugetlb: allow hugepage allocations to excessively
reclaim
On 10/7/19 9:55 AM, Michal Hocko wrote:
> From: David Rientjes <rientjes@...gle.com>
Nit: the subject is still somewhat misleading IMHO, especially in light
of Mike's responses. I would say "reclaim as needed" instead of
"excessively reclaim". The excessive reclaim behavior in hugetlb nr_pages
setting was a bug that was addressed by a different series.
...
> [mhocko@...e.com: reworded changelog]
> Fixes: b39d0ee2632d ("mm, page_alloc: avoid expensive reclaim when compaction may not succeed")
> Cc: Mike Kravetz <mike.kravetz@...cle.com>
> Signed-off-by: David Rientjes <rientjes@...gle.com>
> Signed-off-by: Michal Hocko <mhocko@...e.com>
I still believe that using __GFP_NORETRY as needed is a cleaner solution
than a check for pageblock order and __GFP_IO, but that can be always
changed later. This patch does fix the hugetlbfs regression, so
Acked-by: Vlastimil Babka <vbabka@...e.cz>
Powered by blists - more mailing lists