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 9664CC433EF for ; Tue, 14 Jun 2022 03:15:56 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 06BE28D0202; Mon, 13 Jun 2022 23:15:56 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 01B6A8D01EE; Mon, 13 Jun 2022 23:15:55 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DFE3E8D0202; Mon, 13 Jun 2022 23:15:55 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id D04FD8D01EE for ; Mon, 13 Jun 2022 23:15:55 -0400 (EDT) Received: from smtpin10.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id A9DDB211E6 for ; Tue, 14 Jun 2022 03:15:55 +0000 (UTC) X-FDA: 79575377070.10.DCADEF0 Received: from mail-pj1-f53.google.com (mail-pj1-f53.google.com [209.85.216.53]) by imf05.hostedemail.com (Postfix) with ESMTP id 5E32510008A for ; Tue, 14 Jun 2022 03:15:54 +0000 (UTC) Received: by mail-pj1-f53.google.com with SMTP id mh16-20020a17090b4ad000b001e8313301f1so423407pjb.1 for ; Mon, 13 Jun 2022 20:15:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=X20XqUG2gPAVpTAbsbAwNoi/uST6VyCpegzSApOjB3E=; b=EmjKAQ1yo9tlCNQ5ShZ8eeDUSVfFmuekpqG7pnCRO/yi8MGB+IW/iz+ISXCJk1Q+cO XDbO2j19zeIuBaQqPByQfy09Oa0z6NBP79DW+f5JyJ6R4OzIfkMuSQPDOhIw44pwguPv 5GA1ZAj+3hp3BCmQMBKEb+KTXliOXaEzulBeWVdp+uUx6DUeL75kkk2gl01PP63vCHNV OlSkKfMVijd0i6MtoMDNNZL+eolM8GfRGt3fmrn9RwB4MSnRbKFYb7tdjjFTmqRV2UX+ bJ++oDBCuEHE4jvFd8lZeY6JsxgWKkjpSTXWZ3AxmwsfsmLK8Oe64Ax6aQWyNRlGpwPq jTgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=X20XqUG2gPAVpTAbsbAwNoi/uST6VyCpegzSApOjB3E=; b=RDvrI3Q9eJZijBA4wsdqEFbIIMQ82L6j4t0IapypnzdxW9mgG3MQ0MFC/Lb1AhFRx2 V9Idf50vTOviHM4rVi4jJEHzQDi1Y+ZLPHMIKLdmeWqTACE50esYIBeZx6BJEEkTbCw1 wDnDjCDAVJIn5jv0yUfZdH9+B7v5+V0ywSwL8Dy/G87cjESB/4fzi18+VYuMo0Fctpn2 T6B+j+YzK50nXz7C6W0W5P3lfWIKROsAbJyG+Why2aY2Bl/ZDKPWY1NI0CKZt/Nb/naS pfFLvNBNGNX6/QbnLl4xCwCdSHLunfNgCGAdkSjH9cB3k8d0Gm+5qjANVZBU3ijtNEzK NL9w== X-Gm-Message-State: AOAM533gfZ1ATiEltEI9xfgxzAVSh7Z8RVIeSIqz0wokgI15Dq12Tlya GrPVEmRHZVjDL/f+VckfrfFksA== X-Google-Smtp-Source: AGRyM1ukUxeZ2cHQoIed+a0v/M0Zp41L5bIUZ6Z3UnO9Gt2OahHai6e2mnsTlgui060S1ZC8xOQjzQ== X-Received: by 2002:a17:902:c244:b0:168:c4c3:e80e with SMTP id 4-20020a170902c24400b00168c4c3e80emr2492000plg.18.1655176553058; Mon, 13 Jun 2022 20:15:53 -0700 (PDT) Received: from localhost ([139.177.225.255]) by smtp.gmail.com with ESMTPSA id x4-20020a170902820400b00163fbb1eec5sm5855864pln.229.2022.06.13.20.15.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Jun 2022 20:15:52 -0700 (PDT) Date: Tue, 14 Jun 2022 11:15:49 +0800 From: Muchun Song To: David Hildenbrand Cc: mike.kravetz@oracle.com, akpm@linux-foundation.org, corbet@lwn.net, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH 3/6] mm: hugetlb_vmemmap: introduce the name HVO Message-ID: References: <20220613063512.17540-1-songmuchun@bytedance.com> <20220613063512.17540-4-songmuchun@bytedance.com> <4a6023f3-0fbd-32cf-7e52-bc72e2b4a407@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4a6023f3-0fbd-32cf-7e52-bc72e2b4a407@redhat.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1655176555; 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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=X20XqUG2gPAVpTAbsbAwNoi/uST6VyCpegzSApOjB3E=; b=25H0AnvGBZJf/3SP2tNtlL+NI64448HcLgWbd9PF7UwBLnH8FUslk7Kagn7MJJcmm8XinA kUjFvRKZwlAtC6O586C6k5BIBZAfv9y9PPEp+BZYLHYFHh/x2AaHJsQNL0C6NDRJnk/iE3 Jhj+jeKmaF1ubdSu8iDmKK/j4Gi11cc= ARC-Authentication-Results: i=1; imf05.hostedemail.com; dkim=pass header.d=bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=EmjKAQ1y; dmarc=pass (policy=none) header.from=bytedance.com; spf=pass (imf05.hostedemail.com: domain of songmuchun@bytedance.com designates 209.85.216.53 as permitted sender) smtp.mailfrom=songmuchun@bytedance.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1655176555; a=rsa-sha256; cv=none; b=FHyvw3jRlBuOvPiGhcJsVPVmUDjaq333i8q4+bEV6WyhYB+NuHpysdykHGvTEK1FQWnpsB SSHyrxGgyTGdIo2duwtfCq7jhL3lDtBl9OeHXBidmlIrKExKkyX2sxbrkIoOkf0/cykWt+ YKU3u5F3/W2vb7te12/FOZFthl44Btc= X-Rspamd-Queue-Id: 5E32510008A X-Rspam-User: X-Stat-Signature: wo6nu5j4xh7j75z5gtw4y5heu3r5h7z9 Authentication-Results: imf05.hostedemail.com; dkim=pass header.d=bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=EmjKAQ1y; dmarc=pass (policy=none) header.from=bytedance.com; spf=pass (imf05.hostedemail.com: domain of songmuchun@bytedance.com designates 209.85.216.53 as permitted sender) smtp.mailfrom=songmuchun@bytedance.com X-Rspamd-Server: rspam04 X-HE-Tag: 1655176554-360209 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 Mon, Jun 13, 2022 at 05:39:59PM +0200, David Hildenbrand wrote: > On 13.06.22 08:35, Muchun Song wrote: > > It it inconvenient to mention the feature of optimizing vmemmap pages associated > > with HugeTLB pages when communicating with others since there is no specific or > > abbreviated name for it when it is first introduced. Let us give it a name HVO > > (HugeTLB Vmemmap Optimization) from now. > > > > This commit also updates the document about "hugetlb_free_vmemmap" by the way > > discussed in thread [1]. > > > > Link: https://lore.kernel.org/all/21aae898-d54d-cc4b-a11f-1bb7fddcfffa@redhat.com/ [1] > > Signed-off-by: Muchun Song > > --- > > Documentation/admin-guide/kernel-parameters.txt | 7 ++++--- > > Documentation/admin-guide/mm/hugetlbpage.rst | 3 +-- > > Documentation/admin-guide/sysctl/vm.rst | 3 +-- > > fs/Kconfig | 13 ++++++------- > > mm/hugetlb_vmemmap.c | 8 ++++---- > > mm/hugetlb_vmemmap.h | 4 ++-- > > 6 files changed, 18 insertions(+), 20 deletions(-) > > > > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > > index 391b43fee93e..7539553b3fb0 100644 > > --- a/Documentation/admin-guide/kernel-parameters.txt > > +++ b/Documentation/admin-guide/kernel-parameters.txt > > @@ -1725,12 +1725,13 @@ > > hugetlb_free_vmemmap= > > [KNL] Reguires CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP > > enabled. > > + Control if HugeTLB Vmemmap Optimization (HVO) is enabled. > > Allows heavy hugetlb users to free up some more > > memory (7 * PAGE_SIZE for each 2MB hugetlb page). > > - Format: { [oO][Nn]/Y/y/1 | [oO][Ff]/N/n/0 (default) } > > + Format: { on | off (default) } > > > > - [oO][Nn]/Y/y/1: enable the feature > > - [oO][Ff]/N/n/0: disable the feature > > + on: enable HVO > > + off: disable HVO > > > > Built with CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON=y, > > the default is on. > > diff --git a/Documentation/admin-guide/mm/hugetlbpage.rst b/Documentation/admin-guide/mm/hugetlbpage.rst > > index a90330d0a837..64e0d5c512e7 100644 > > --- a/Documentation/admin-guide/mm/hugetlbpage.rst > > +++ b/Documentation/admin-guide/mm/hugetlbpage.rst > > @@ -164,8 +164,7 @@ default_hugepagesz > > will all result in 256 2M huge pages being allocated. Valid default > > huge page size is architecture dependent. > > hugetlb_free_vmemmap > > - When CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP is set, this enables optimizing > > - unused vmemmap pages associated with each HugeTLB page. > > + When CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP is set, this enables HVO. > > Heh, it would be convenient to call this > > CONFIG_HUGETLB_PAGE_VMEMMAP_OPTIMIZATION (HVO) then. > Thanks for pointing it out. I would take Mike's suggestion. I would change to: When CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP is set this enables HugeTLB Vmemmap Optimization (HVO). Thanks.