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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 379D9C433EF for ; Fri, 10 Jun 2022 09:36:00 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C8D856B0156; Fri, 10 Jun 2022 05:35:59 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id C157E6B0155; Fri, 10 Jun 2022 05:35:59 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id ADD7C8D0086; Fri, 10 Jun 2022 05:35:59 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 9AF846B0154 for ; Fri, 10 Jun 2022 05:35:59 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 6F3E220D43 for ; Fri, 10 Jun 2022 09:35:59 +0000 (UTC) X-FDA: 79561819638.11.8266FA2 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by imf18.hostedemail.com (Postfix) with ESMTP id 5DA1F1C006B for ; Fri, 10 Jun 2022 09:35:58 +0000 (UTC) Received: from dggpemm500021.china.huawei.com (unknown [172.30.72.54]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4LKG4W0dLlzdZvG; Fri, 10 Jun 2022 17:34:03 +0800 (CST) Received: from dggpemm500001.china.huawei.com (7.185.36.107) by dggpemm500021.china.huawei.com (7.185.36.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 10 Jun 2022 17:35:54 +0800 Received: from [10.174.177.243] (10.174.177.243) by dggpemm500001.china.huawei.com (7.185.36.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 10 Jun 2022 17:35:53 +0800 Message-ID: Date: Fri, 10 Jun 2022 17:35:52 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH v3 4/6] mm: Demote warning message in vmemmap_verify() to debug level Content-Language: en-US To: mawupeng , , , , , , CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , References: <20220607093805.1354256-1-mawupeng1@huawei.com> <20220607093805.1354256-5-mawupeng1@huawei.com> <1f2a76d5-7c4e-46bc-ce66-20a962eac73c@arm.com> <8d5e867f-e51a-d763-5ac3-6dfc4e67a376@huawei.com> From: Kefeng Wang In-Reply-To: <8d5e867f-e51a-d763-5ac3-6dfc4e67a376@huawei.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.177.243] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To dggpemm500001.china.huawei.com (7.185.36.107) X-CFilter-Loop: Reflected ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1654853759; a=rsa-sha256; cv=none; b=to4C0SuVhPZZxsAzkRYGcRx7a+qdI5oiCbqzTrDdQkRjUzmDmk/oXOxJKiyzkljj9yIMDg bfm5pfSqzPieD8/jZTdtgPIRAqliZ92qIPMCQMQA58dBylDvxG4bDEHNzLqa6CfjWXvoKf 40RfrSTR+QgPQoZmV5meOKi7afcQY7Y= ARC-Authentication-Results: i=1; imf18.hostedemail.com; dkim=none; spf=pass (imf18.hostedemail.com: domain of wangkefeng.wang@huawei.com designates 45.249.212.187 as permitted sender) smtp.mailfrom=wangkefeng.wang@huawei.com; dmarc=pass (policy=quarantine) header.from=huawei.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1654853759; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KMds9ebxCj972Zfv0Is4xHDNgxdIPmGYDY6fRdBbYwc=; b=ZWio7Hjy23gnpkJ52tpokSD/QZULZdvJD+mJb61Fza34+q9PalfQPxwcZcrNDu57k5Lz7G A3hBlIsDGloTk1HjVOBiTrOi+Q+EQIWzi4xcPPBhhjMrT9TftSt63GnwXD8AEYrn9aQA+H yoO/Tka5XcWK48CiFQ3rTQObHiMhtdc= X-Rspamd-Server: rspam09 X-Rspamd-Queue-Id: 5DA1F1C006B X-Stat-Signature: 7rpmfgqp5ophdqo8g35hofxqhibfaqeu X-Rspam-User: Authentication-Results: imf18.hostedemail.com; dkim=none; spf=pass (imf18.hostedemail.com: domain of wangkefeng.wang@huawei.com designates 45.249.212.187 as permitted sender) smtp.mailfrom=wangkefeng.wang@huawei.com; dmarc=pass (policy=quarantine) header.from=huawei.com X-HE-Tag: 1654853758-517856 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 2022/6/9 16:13, mawupeng wrote: > > > 在 2022/6/8 18:00, Anshuman Khandual 写道: >> >> >> On 6/8/22 06:56, mawupeng wrote: >>> >>> >>> 在 2022/6/7 20:25, David Hildenbrand 写道: >>>> On 07.06.22 11:38, Wupeng Ma wrote: >>>>> From: Ma Wupeng >>>>> >>>>> For a system only have limited mirrored memory or some numa node >>>>> without >>>>> mirrored memory, the per node vmemmap page_structs prefer to allocate >>>>> memory from mirrored region, which will lead to vmemmap_verify() in >>>>> vmemmap_populate_basepages() report lots of warning message. >>>>> >>>>> This patch demote the "potential offnode page_structs" warning >>>>> messages >>>>> to debug level to avoid a very long print during bootup. >>>>> >>>>> Signed-off-by: Ma Wupeng >>>>> --- >>>>>    mm/sparse-vmemmap.c | 2 +- >>>>>    1 file changed, 1 insertion(+), 1 deletion(-) >>>>> >>>>> diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c >>>>> index f4fa61dbbee3..78debdb89eb1 100644 >>>>> --- a/mm/sparse-vmemmap.c >>>>> +++ b/mm/sparse-vmemmap.c >>>>> @@ -528,7 +528,7 @@ void __meminit vmemmap_verify(pte_t *pte, int >>>>> node, >>>>>        int actual_node = early_pfn_to_nid(pfn); >>>>>          if (node_distance(actual_node, node) > LOCAL_DISTANCE) >>>>> -        pr_warn("[%lx-%lx] potential offnode page_structs\n", >>>>> +        pr_debug("[%lx-%lx] potential offnode page_structs\n", >>>>>                start, end - 1); >>>>>    } >>>> >>>> This will possibly hide it in environments where this might indeed >>>> indicate performance issues. >>>> >>>> What about a pr_warn_once()? >>>> >>> >>> Sure. >>> >>> This will works. We can certainly use a pr_warn_once(). >> >> Why not pr_warn_ratelimited() like in the previous patch ? > > Function vmemmap_populate_basepages() is used to populate base pages. > System with huge memory will produce lots lots of warning message > during this populate process even with ratelimited. This may lead to slow > startup. I think pr_warn_once is better, the memblock_alloc fallback is not frequent, but vmemmap_verify will verify each memory and print a lot. > > Thanks for reviewing. > >> . > .