Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp6653906rwr; Tue, 9 May 2023 19:27:44 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5kjeqgQwdto9266wXZmGLC1vcuXw93qCAF9KOnFrMk+pfep5hXQVUw9DtrDjvMdH2fRafU X-Received: by 2002:a05:6a20:12c9:b0:100:b715:8ab2 with SMTP id v9-20020a056a2012c900b00100b7158ab2mr10412414pzg.46.1683685663710; Tue, 09 May 2023 19:27:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683685663; cv=none; d=google.com; s=arc-20160816; b=tGVdQ7B7d1Bt+VWlU6ygPdZJ7SENmIa7Z4c4fskyWIXuumByxyBFsHUep5GJrSM43B nnjJBHesykbtt/cNGkhHkkuVH4Fh1ygqGrhmdiULxjomJVn2ZnulAR810q5cbSiYpuZK MrX2qGo0jqcQjGOzUZhAwm13m49GSbN3WYQ/7QNkI/Vth/Y1/RW8D7AtccXE8hZ1/vh0 IjL0vztM8dLcGKZCPqUU+dOgtSBz7b2lon/XK+fX9vxfUASUrXeYkL2y9rbhRXQUSlW1 bW8Q6ZSAeQGF8wSnx9AUUEEtdZspvWyFl1bnRPVXsZqFbIVVMpMFztrvSivTkI6WPPri k3XA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:subject:to:from; bh=PQCIijOL/uAK4ELWEeeMgdchyBkBMDzvQtR6BnGtZHw=; b=FqSkV/LD/lAFu6Da0OzskEua+qdfwY1JF+ZNGCpnMD4Z1DYxE2QBz3Fqvj36WvwkCH /KJ6/wTNvSsh0qtKjpn6J9BesEGVZKE+a1qVRbxrC4n2IOOjlPXBTmrWgzZXxhgwSEI4 OeCUyPRl6KE3LfbOeC7KruHPJSYQ2vtXVzeWzGrJBF2V/zRS4hZK/HwgpkisWkGAFsiB QnqPPlWJRfMLxCM6SglyG3fxZ3bcJrDb1H30QjAFY2Io8OqhdZ3sGzjcRRcSGwcY6SB8 QlD9JXlssKVsbiGaVT5vP0fiCThLXdE52vkM3j9BarLjkO5bHLFS47PUvDZOBW274MgH EgFg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bt30-20020a63291e000000b00520d737cf49si2737591pgb.271.2023.05.09.19.27.31; Tue, 09 May 2023 19:27:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235045AbjEJCWC (ORCPT + 99 others); Tue, 9 May 2023 22:22:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41942 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234970AbjEJCWA (ORCPT ); Tue, 9 May 2023 22:22:00 -0400 Received: from SHSQR01.spreadtrum.com (mx1.unisoc.com [222.66.158.135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4ED3118 for ; Tue, 9 May 2023 19:21:54 -0700 (PDT) Received: from SHSend.spreadtrum.com (bjmbx01.spreadtrum.com [10.0.64.7]) by SHSQR01.spreadtrum.com with ESMTP id 34A2L8Yv001544; Wed, 10 May 2023 10:21:08 +0800 (+08) (envelope-from zhaoyang.huang@unisoc.com) Received: from bj03382pcu.spreadtrum.com (10.0.74.65) by BJMBX01.spreadtrum.com (10.0.64.7) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 10 May 2023 10:21:06 +0800 From: "zhaoyang.huang" To: Andrew Morton , Roman Gushchin , Minchan Kim , Roman Gushchin , Joonsoo Kim , , , Zhaoyang Huang , Subject: [PATCHv4] mm: optimization on page allocation when CMA enabled Date: Wed, 10 May 2023 10:20:51 +0800 Message-ID: <1683685251-2059-1-git-send-email-zhaoyang.huang@unisoc.com> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.0.74.65] X-ClientProxiedBy: SHCAS03.spreadtrum.com (10.0.1.207) To BJMBX01.spreadtrum.com (10.0.64.7) X-MAIL: SHSQR01.spreadtrum.com 34A2L8Yv001544 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Zhaoyang Huang Let us look at the series of scenarios below with WMARK_LOW=25MB,WMARK_MIN=5MB (managed pages 1.9GB). We can know that current 'fixed 1/2 ratio' start to use CMA since C which actually has caused U&R lower than WMARK_LOW (this should be deemed as against current memory policy, that is, UNMOVABLE & RECLAIMABLE should either stay around WATERMARK_LOW when no allocation or do reclaim via entering slowpath) -- Free_pages | | -- WMARK_LOW | -- Free_CMA | | -- Free_CMA/Free_pages(MB) A(12/30) B(12/25) C(12/20) fixed 1/2 ratio N N Y this commit Y Y Y Signed-off-by: Zhaoyang Huang --- v2: do proportion check when zone_watermark_ok, update commit message v3: update coding style and simplify the logic when zone_watermark_ok v4: code update according to Roman's suggest --- --- mm/page_alloc.c | 44 ++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 40 insertions(+), 4 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 0745aed..4719800 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -3071,6 +3071,43 @@ static bool unreserve_highatomic_pageblock(const struct alloc_context *ac, } +#ifdef CONFIG_CMA +/* + * GFP_MOVABLE allocation could drain UNMOVABLE & RECLAIMABLE page blocks via + * the help of CMA which makes GFP_KERNEL failed. Checking if zone_watermark_ok + * again without ALLOC_CMA to see if to use CMA first. + */ +static bool use_cma_first(struct zone *zone, unsigned int order, unsigned int alloc_flags) +{ + unsigned long watermark; + bool cma_first = false; + + watermark = wmark_pages(zone, alloc_flags & ALLOC_WMARK_MASK); + /* check if GFP_MOVABLE pass previous zone_watermark_ok via the help of CMA */ + if (zone_watermark_ok(zone, order, watermark, 0, alloc_flags & (~ALLOC_CMA))) { + /* + * Balance movable allocations between regular and CMA areas by + * allocating from CMA when over half of the zone's free memory + * is in the CMA area. + */ + cma_first = (zone_page_state(zone, NR_FREE_CMA_PAGES) > + zone_page_state(zone, NR_FREE_PAGES) / 2); + } else { + /* + * watermark failed means UNMOVABLE & RECLAIMBLE is not enough + * now, we should use cma first to keep them stay around the + * corresponding watermark + */ + cma_first = true; + } + return cma_first; +} +#else +static bool use_cma_first(struct zone *zone, unsigned int order, unsigned int alloc_flags) +{ + return false; +} +#endif /* * Do the hard work of removing an element from the buddy allocator. * Call me with the zone->lock already held. @@ -3084,12 +3121,11 @@ static bool unreserve_highatomic_pageblock(const struct alloc_context *ac, if (IS_ENABLED(CONFIG_CMA)) { /* * Balance movable allocations between regular and CMA areas by - * allocating from CMA when over half of the zone's free memory - * is in the CMA area. + * allocating from CMA base on judging zone_watermark_ok again + * to see if the latest check got pass via the help of CMA */ if (alloc_flags & ALLOC_CMA && - zone_page_state(zone, NR_FREE_CMA_PAGES) > - zone_page_state(zone, NR_FREE_PAGES) / 2) { + use_cma_first(zone, order, alloc_flags)) { page = __rmqueue_cma_fallback(zone, order); if (page) return page; -- 1.9.1