From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9D816C4BA0F for ; Wed, 26 Feb 2020 08:08:03 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 6CD3A20714 for ; Wed, 26 Feb 2020 08:08:03 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6CD3A20714 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=techsingularity.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 177666B0006; Wed, 26 Feb 2020 03:08:03 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 128846B0007; Wed, 26 Feb 2020 03:08:03 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 03D1E6B0008; Wed, 26 Feb 2020 03:08:02 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0127.hostedemail.com [216.40.44.127]) by kanga.kvack.org (Postfix) with ESMTP id DD3A46B0006 for ; Wed, 26 Feb 2020 03:08:02 -0500 (EST) Received: from smtpin01.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id AE0A1180AD811 for ; Wed, 26 Feb 2020 08:08:02 +0000 (UTC) X-FDA: 76531550004.01.lift30_46289d8e98e50 X-HE-Tag: lift30_46289d8e98e50 X-Filterd-Recvd-Size: 3209 Received: from outbound-smtp49.blacknight.com (outbound-smtp49.blacknight.com [46.22.136.233]) by imf40.hostedemail.com (Postfix) with ESMTP for ; Wed, 26 Feb 2020 08:08:01 +0000 (UTC) Received: from mail.blacknight.com (pemlinmail01.blacknight.ie [81.17.254.10]) by outbound-smtp49.blacknight.com (Postfix) with ESMTPS id 29F10FA851 for ; Wed, 26 Feb 2020 08:08:00 +0000 (GMT) Received: (qmail 13849 invoked from network); 26 Feb 2020 08:08:00 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.18.57]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 26 Feb 2020 08:07:59 -0000 Date: Wed, 26 Feb 2020 08:07:57 +0000 From: Mel Gorman To: David Rientjes Cc: Andrew Morton , Michal Hocko , Vlastimil Babka , Ivan Babrou , Rik van Riel , Linux-MM , Linux Kernel Mailing List Subject: Re: [PATCH 2/3] mm, page_alloc: Disable watermark boosting if THP is disabled at boot Message-ID: <20200226080757.GB3818@techsingularity.net> References: <20200225141534.5044-1-mgorman@techsingularity.net> <20200225141534.5044-3-mgorman@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Feb 25, 2020 at 05:32:24PM -0800, David Rientjes wrote: > On Tue, 25 Feb 2020, Mel Gorman wrote: > > > Watermark boosting is intended to increase the success rate and reduce > > latency of high-order allocations, particularly THP. If THP is disabled > > at boot, then it makes sense to disable watermark boosting as well. While > > there are other high-order allocations that potentially benefit, they > > are relatively rare. > > > > Signed-off-by: Mel Gorman > > --- > > mm/huge_memory.c | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/mm/huge_memory.c b/mm/huge_memory.c > > index b08b199f9a11..565bb9973ff8 100644 > > --- a/mm/huge_memory.c > > +++ b/mm/huge_memory.c > > @@ -472,6 +472,7 @@ static int __init setup_transparent_hugepage(char *str) > > &transparent_hugepage_flags); > > clear_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG, > > &transparent_hugepage_flags); > > + disable_watermark_boosting(); > > ret = 1; > > } > > out: > > Seems like watermark boosting can help prevent fragmentation so it > benefits all hugepage sized allocations for the long term and that would > include dynamic provisioning of hugetlb memory or hugetlb overcommit? Yes but it's very rare to hear of cases where hugetlb is dynamically provisioned or overcommitted once THP existed and stopped stalling the system excessively. I'm happy enough to drop this patch because I'm not relying on it in the context of this bug. -- Mel Gorman SUSE Labs