From patchwork Fri Sep 9 09:24:51 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Miaohe Lin X-Patchwork-Id: 12971384 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 D5E56ECAAD3 for ; Fri, 9 Sep 2022 09:25:53 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 2EE3D80008; Fri, 9 Sep 2022 05:25:36 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 2766B80007; Fri, 9 Sep 2022 05:25:36 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 13CB980008; Fri, 9 Sep 2022 05:25:35 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id E3D4C80007 for ; Fri, 9 Sep 2022 05:25:35 -0400 (EDT) Received: from smtpin16.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id B80491209B7 for ; Fri, 9 Sep 2022 09:25:35 +0000 (UTC) X-FDA: 79892014230.16.C0FBD9E Received: from szxga08-in.huawei.com (szxga08-in.huawei.com [45.249.212.255]) by imf19.hostedemail.com (Postfix) with ESMTP id 3045F1A0064 for ; Fri, 9 Sep 2022 09:25:34 +0000 (UTC) Received: from canpemm500002.china.huawei.com (unknown [172.30.72.57]) by szxga08-in.huawei.com (SkyGuard) with ESMTP id 4MP9VF6LxPz14QMg; Fri, 9 Sep 2022 17:21:41 +0800 (CST) Received: from huawei.com (10.175.124.27) by canpemm500002.china.huawei.com (7.192.104.244) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 9 Sep 2022 17:25:32 +0800 From: Miaohe Lin To: CC: , , , , Subject: [PATCH 16/16] mm/page_alloc: fix obsolete comment in deferred_pfn_valid() Date: Fri, 9 Sep 2022 17:24:51 +0800 Message-ID: <20220909092451.24883-17-linmiaohe@huawei.com> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20220909092451.24883-1-linmiaohe@huawei.com> References: <20220909092451.24883-1-linmiaohe@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.175.124.27] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To canpemm500002.china.huawei.com (7.192.104.244) X-CFilter-Loop: Reflected ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1662715535; a=rsa-sha256; cv=none; b=19THQMkH488YVcM5iEPReWuD2hH5+dhwZZRjaoycc0S6cWo/BYP/BrrNBi0ZxskG7Xapog jfywowVR+fKmxJbJlkkf/j3l8UO5JyGBsy6w7ljTTI/j8PDH42AoG4eeUP40h5s+lBPRx7 mmCpFmiCHBNStHjKdDSfZPMQkk0FVPY= ARC-Authentication-Results: i=1; imf19.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf19.hostedemail.com: domain of linmiaohe@huawei.com designates 45.249.212.255 as permitted sender) smtp.mailfrom=linmiaohe@huawei.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1662715535; 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=bNGFGqFklJ+pmLbiqmbaNHlp+lsEPj9bnosN9vpHVhU=; b=gSpNCN3ZbqwqmIJUQ+fVKKlBXyqwISN+TXkf13/+YHvCrzEuCqHnutyqeqPMpPrwfyX8tI ahEIWFY+BGbJdsrMXKRAvbxgCetgWFyMQ/AjHN00FLYO1L5aqIQxxvVmu1wuUyTzFqTcsc 6Gh2U7MNHgsNy27ocJPKVVHAMjQWIYg= X-Stat-Signature: 8tfmqjps6584eedbo13ypep9ykhfefgu X-Rspamd-Queue-Id: 3045F1A0064 X-Rspam-User: Authentication-Results: imf19.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf19.hostedemail.com: domain of linmiaohe@huawei.com designates 45.249.212.255 as permitted sender) smtp.mailfrom=linmiaohe@huawei.com X-Rspamd-Server: rspam12 X-HE-Tag: 1662715534-849570 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: There are no architectures that can have holes in the memory map within a pageblock since commit 859a85ddf90e ("mm: remove pfn_valid_within() and CONFIG_HOLES_IN_ZONE"). Update the corresponding comment. Signed-off-by: Miaohe Lin Reviewed-by: David Hildenbrand Reviewed-by: Anshuman Khandual Reviewed-by: Oscar Salvador --- mm/page_alloc.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 262e8972e019..4cc0232020d2 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1929,11 +1929,7 @@ static inline void __init pgdat_init_report_one_done(void) /* * Returns true if page needs to be initialized or freed to buddy allocator. * - * First we check if pfn is valid on architectures where it is possible to have - * holes within pageblock_nr_pages. On systems where it is not possible, this - * function is optimized out. - * - * Then, we check if a current large page is valid by only checking the validity + * We check if a current large page is valid by only checking the validity * of the head pfn. */ static inline bool __init deferred_pfn_valid(unsigned long pfn)