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 8B45AC433EF for ; Sun, 28 Nov 2021 11:19:22 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id D46636B0075; Sun, 28 Nov 2021 06:19:11 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id CF5BA6B0078; Sun, 28 Nov 2021 06:19:11 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id BE50A6B007B; Sun, 28 Nov 2021 06:19:11 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0202.hostedemail.com [216.40.44.202]) by kanga.kvack.org (Postfix) with ESMTP id ABCCF6B0075 for ; Sun, 28 Nov 2021 06:19:11 -0500 (EST) Received: from smtpin13.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 684F61803032D for ; Sun, 28 Nov 2021 11:19:01 +0000 (UTC) X-FDA: 78858092082.13.4FC7D11 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf15.hostedemail.com (Postfix) with ESMTP id 9BD84D0000A4 for ; Sun, 28 Nov 2021 11:18:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1638098340; h=from:from: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; bh=UGK+Dn6UZl9sr7vGdBkJU4cqFeth9dYn+pKxQkt6tRs=; b=eJMHp7tQlsWEWGpfub7gBbnOZ18x3OYp+wzpFUHSNA9JzkIrriLy+dsgTtphG1F7RpjJ4I 4KGL/wsF/gcimWflxv6elQmrifGRfWzp/yAQWOqfPBMN/TyNOSi/WB8GrQ03x/CrVaY4os oLQS7fHMMF1zTSaBB4oH085oT15g3yI= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-288-oWx_jglROaGSvA8_QSgh_g-1; Sun, 28 Nov 2021 06:18:56 -0500 X-MC-Unique: oWx_jglROaGSvA8_QSgh_g-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9E98B1006AA0; Sun, 28 Nov 2021 11:18:55 +0000 (UTC) Received: from starship (unknown [10.40.192.24]) by smtp.corp.redhat.com (Postfix) with ESMTP id DADEC60854; Sun, 28 Nov 2021 11:18:53 +0000 (UTC) Message-ID: Subject: Commit 'hugetlbfs: extend the definition of hugepages parameter to support node allocation' breaks old numa less syntax of reserving hugepages on boot. From: Maxim Levitsky To: Zhenguo Yao Cc: Mike Kravetz , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org Date: Sun, 28 Nov 2021 13:18:52 +0200 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Stat-Signature: rfbwy9x3pm9jp6sy4wet64rf3krjkzxd X-Rspamd-Queue-Id: 9BD84D0000A4 X-Rspamd-Server: rspam07 Authentication-Results: imf15.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=eJMHp7tQ; spf=none (imf15.hostedemail.com: domain of mlevitsk@redhat.com has no SPF policy when checking 170.10.133.124) smtp.mailfrom=mlevitsk@redhat.com; dmarc=pass (policy=none) header.from=redhat.com X-HE-Tag: 1638098334-769046 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: dmesg prints this: HugeTLB: allocating 64 of page size 1.00 GiB failed. Only allocated 0 hugepages Huge pages were allocated on kernel command line (1/2 of 128GB system): 'default_hugepagesz=1G hugepagesz=1G hugepages=64' This is 3970X and no real support/need for NUMA, thus only fake NUMA node 0 is present. Reverting the commit helps. New syntax also works ( hugepages=0:64 ) I can test any patches for this bug. Also unrelated, is there any progress on allocating 1GB pages on demand so that I could allocate them only when I run a VM? i don't mind having these pages to be marked as to be used for userspace only, since as far as I remember its the kernel usage that makes some page unmoveable. Last time (many years ago) I tried to create a zone with only userspace pages (I don't remember what options I used) but it didn't work. Is there a way to debug what is causing unmoveable pages and doesn't let /proc/sys/vm/nr_hugepages work (I tried it today and as usual the number it can allocate steadly decreases over time). Thanks, Best regards, Maxim Levitsky