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 X-Spam-Level: X-Spam-Status: No, score=-6.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3F0D4C4338F for ; Sun, 22 Aug 2021 22:19:56 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id BFB4F6127B for ; Sun, 22 Aug 2021 22:19:55 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org BFB4F6127B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id CF9896B006C; Sun, 22 Aug 2021 18:19:54 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id CAAA16B0072; Sun, 22 Aug 2021 18:19:54 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B989E6B0073; Sun, 22 Aug 2021 18:19:54 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0157.hostedemail.com [216.40.44.157]) by kanga.kvack.org (Postfix) with ESMTP id 9BEAF6B006C for ; Sun, 22 Aug 2021 18:19:54 -0400 (EDT) Received: from smtpin05.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 3259C180BD77E for ; Sun, 22 Aug 2021 22:19:54 +0000 (UTC) X-FDA: 78504135108.05.813FD52 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf23.hostedemail.com (Postfix) with ESMTP id C699A90000A6 for ; Sun, 22 Aug 2021 22:19:53 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 892AF61267; Sun, 22 Aug 2021 22:19:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1629670792; bh=9QiEIQNGBi9nfvqgJV5eTtXQ+nYy4w+IVMveVo1QNHI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=KC9ACjBAbvdERDZUfnmGTzJOxTRFJU9//f1GKDlopXubbyDOcDgvh6S6vlaqgpw1p KmmoRTO6nNFOlNV7MhikA4K6QoOIshP2cQFp9+YAmuApcP2Idu51qqrCYIK5IBWwQH LKmuFexhzTPa/fzt0YJ0SYVPShbkgpbpwUdnU48U= Date: Sun, 22 Aug 2021 15:19:52 -0700 From: Andrew Morton To: yaozhenguo Cc: mike.kravetz@oracle.com, corbet@lwn.net, yaozhenguo@jd.com, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH] hugetlbfs: add hugepages_node kernel parameter Message-Id: <20210822151952.23ca9547316dc34c9f3bd482@linux-foundation.org> In-Reply-To: <20210820030536.25737-1-yaozhenguo1@gmail.com> References: <20210820030536.25737-1-yaozhenguo1@gmail.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=KC9ACjBA; dmarc=none; spf=pass (imf23.hostedemail.com: domain of akpm@linux-foundation.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: C699A90000A6 X-Stat-Signature: wnwfbunzio43fnmfkafwakw63e54g3ua X-HE-Tag: 1629670793-658225 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 Fri, 20 Aug 2021 11:05:36 +0800 yaozhenguo wrote: > We can specify the number of hugepages to allocate at boot. But the > hugepages is balanced in all nodes at present. In some scenarios, > we only need hugepags in one node. For example: DPDK needs hugepages > which is in the same node as NIC. if DPDK needs four hugepags of 1G > size in node1 and system has 16 numa nodes. We must reserve 64 hugepags > in kernel cmdline. But, only four hugepages is used. The others should > be free after boot.If the system memory is low(for example: 64G), it will > be an impossible task. So, add hugepages_node kernel parameter to specify > node number of hugepages to allocate at boot. > For example add following parameter: > > hugepagesz=1G hugepages_node=1 hugepages=4 > > It will allocate 4 hugepags in node1 at boot. If were going to do this, shouldn't we permit more than one node? hugepages_nodes=1,2,5