Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp8304644rwr; Wed, 10 May 2023 22:25:41 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7Fz/vGGWELS9+AIwkOPoKlfz8mc8RNiyz5FPiYHl9GrqCbO5b1Xt6EYcktJlIibi1rpZyX X-Received: by 2002:a17:903:22cd:b0:1aa:ebcc:dd5e with SMTP id y13-20020a17090322cd00b001aaebccdd5emr23861410plg.65.1683782740666; Wed, 10 May 2023 22:25:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683782740; cv=none; d=google.com; s=arc-20160816; b=05tp5nXlloo9Od2whD8rLCPw2h4trd94OQDM/3Yk5soC5La7g52V+0IeKeYOZGa6cu Mro5AArR9oY0bcdigdrLd2Hwg6V4GYSJQ/LcdQIXW5l6YW7Tf5j6vjJg/NfIkgBk5Efx 1fVijAHAqLb0pBdzNHmteO79bmk1Ebf6wo+pEBnRPi9J4l6wGU1LPkSoJckFSG05GfiE k4XyELRQdOy628iPI9JaBKqZZiI9dYnpx4OQtxTHdMqQGksaCIJgug2qa2A4ObFBshIz 4QiLYo8n5NFOzwc8CxZwTBj2LTXltria93FUNyvfRtWVCGyvjyzWUp7pBhd2HdYn3761 Numg== 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=LdsTI0B0sR0dWH8uXtsF4wlOe+BmEUWOB5z9Wpzc034=; b=xledRl1srDfz9yg3WYcTpG6lP/W8HShS1thPscld3oEm5v1We0XNWKyFBS7NRVQnGW TTaMTm9VyZYcxCvYVmHFhrDhQbjawuYlxThIX/FInPh0tXb8prn1mZfMigIB/6nPAq5Z jLx78CuzH0+hbDA7NjJShwy3YRFtIKXNo9uW62px6D0e82NJSo7COjfQoQdnN37zRsIJ B755+rqIygY3Yp+WtOYXHnxgP5Em5Z4o234w+tVc3oUa2HgnIMLmKGt4Zqvx0vBuMDT5 k22hUpy7WbRXdLMM5ueoY2gkU7ejCBC89Grip78vVI/tae0w8EkjvvxrBKvZBH0f0R/z cbLA== 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 e1-20020a17090301c100b001a51bb4ad79si5868634plh.42.2023.05.10.22.25.28; Wed, 10 May 2023 22:25:40 -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 S229535AbjEKFYg (ORCPT + 99 others); Thu, 11 May 2023 01:24:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44640 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236939AbjEKFYb (ORCPT ); Thu, 11 May 2023 01:24:31 -0400 Received: from SHSQR01.spreadtrum.com (unknown [222.66.158.135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C6A4E61A2 for ; Wed, 10 May 2023 22:23:57 -0700 (PDT) Received: from SHSend.spreadtrum.com (bjmbx01.spreadtrum.com [10.0.64.7]) by SHSQR01.spreadtrum.com with ESMTP id 34B5MmNo050137; Thu, 11 May 2023 13:22:48 +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; Thu, 11 May 2023 13:22:44 +0800 From: "zhaoyang.huang" To: Andrew Morton , Roman Gushchin , Minchan Kim , Roman Gushchin , Joonsoo Kim , , , Zhaoyang Huang , Subject: [PATCHv5] mm: optimization on page allocation when CMA enabled Date: Thu, 11 May 2023 13:22:30 +0800 Message-ID: <1683782550-25799-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 34B5MmNo050137 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 timeline of scenarios below with WMARK_LOW=25MB WMARK_MIN=5MB (managed pages 1.9GB). We can find that CMA begin to be used until 'C' under the method of 'fixed 2 times of free cma over free pages' which could have the scenario 'A' and 'B' into a fault state, that is, free UNMOVABLE & RECLAIMABLE pages is lower than corresponding watermark without reclaiming which should be deemed as against current memory policy. This commit try to solve this by checking zone_watermark_ok again with removing CMA pages which could lead to a proper time point of CMA's utilization. -- 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 v5: update commit message --- --- 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