Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp1860116rwr; Fri, 5 May 2023 23:49:59 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6lBQDDV12DujtBLxS01RAJvOAVa/nFFZdMaFly7MawR5JrFCRliUbqy/wwk2qXhTdbfUK/ X-Received: by 2002:a05:6a20:1606:b0:f5:4edd:d831 with SMTP id l6-20020a056a20160600b000f54eddd831mr5053937pzj.57.1683355799156; Fri, 05 May 2023 23:49:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683355799; cv=none; d=google.com; s=arc-20160816; b=uwuvoOCkQWxwrMfWdMnsY1Jg98i4t/UYuEgMC/r0Q95HQpgq3/A5HQiyB5IzxAGymw GyJy5/cjhWsFRqlGzoxCJbc/7H/VY7IzkSVPOiUDLa9X3XEKPehDkdTMbjZzwFGm82d8 HcfeayxwUi4duQ4XjY/ptCd9OFJFpI318f7kEuldXo6B60MsBUm/amM3pu7oQVjvMFaP 3kmVqUnT/cBqaSd8xZEqgNyh4LKWAo7rgLS/U34TOmMPcUltIKUcKck9xZMHielKGboh qR3GY3r8TM/h4cTcjb2E6cS4lrWHmR3yTRLt5XJqaRTE4+eK+wfPU7nSP6oCLZ8IqNWB RMSw== 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=05B9HLEVIXOyu73vSo8T/gNbsWk1TAFnDf+P1UFDg/w=; b=jAJSDLMlCtd91wvqQaVr7KbCLBtQveCAYDCTCZjpW8iPvz8nOpGIxaEyckVzVYgqdK 2rpbilD7MqbVLYL+n6w5uUvRDgGJh2EkedV4BzP8tT14JmvBzg6aBeFIsCpfb55KHoTu /ZFGbDbXw63CwYhwuGhsHpaJf9bv6sRBlO8c6lAI1jmMPDjmnFKcBvF38UjJM1lwaZVM +cFgqkEWdMNypUFOXHFo8mF24Tgbuts6lQ0lDhORa+dnWoAJUgaeKkpBdkX4KC8zYc3b 5yjR44PaMO29d2czRyKO2U8eSukogqgokR4s825WVrkDW6dQlXtGFWTM14k1ccaTueia y45g== 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 j13-20020a63cf0d000000b005137bf7e2d4si3924286pgg.652.2023.05.05.23.49.31; Fri, 05 May 2023 23:49:59 -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 S230196AbjEFGq7 (ORCPT + 99 others); Sat, 6 May 2023 02:46:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50824 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229602AbjEFGq6 (ORCPT ); Sat, 6 May 2023 02:46:58 -0400 Received: from SHSQR01.spreadtrum.com (mx1.unisoc.com [222.66.158.135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 22B2B30FD for ; Fri, 5 May 2023 23:46:55 -0700 (PDT) Received: from SHSend.spreadtrum.com (bjmbx01.spreadtrum.com [10.0.64.7]) by SHSQR01.spreadtrum.com with ESMTP id 3466k8e5050232; Sat, 6 May 2023 14:46:09 +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; Sat, 6 May 2023 14:46:06 +0800 From: "zhaoyang.huang" To: Andrew Morton , Roman Gushchin , Minchan Kim , Roman Gushchin , Joonsoo Kim , , , Zhaoyang Huang , Subject: [PATCHv3] mm: optimization on page allocation when CMA enabled Date: Sat, 6 May 2023 14:45:47 +0800 Message-ID: <1683355547-10524-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 3466k8e5050232 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 --- --- mm/page_alloc.c | 46 ++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 40 insertions(+), 6 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 0745aed..7aca49d 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -3071,6 +3071,41 @@ 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 __if_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))) + /* + * 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; + else + /* + * remain previous fixed 1/2 logic when watermark ok as we have + * above protection now + */ + cma_first = (zone_page_state(zone, NR_FREE_CMA_PAGES) > + zone_page_state(zone, NR_FREE_PAGES) / 2); + return cma_first; +} +#else +static bool __if_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,13 +3119,12 @@ 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) { - page = __rmqueue_cma_fallback(zone, order); + if (migratetype == MIGRATE_MOVABLE) { + page = __if_use_cma_first(zone, order, alloc_flags) ? + __rmqueue_cma_fallback(zone, order) : NULL; if (page) return page; } -- 1.9.1