Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mQuy8-0002xC-DP for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Sep 2021 17:14:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mQuy5-0001tb-UY for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Sep 2021 17:14:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mQuy5-0001tT-Iq for pgsql-hackers@lists.postgresql.org; Thu, 16 Sep 2021 17:14:37 +0000 Received: from mail-il1-x131.google.com ([2607:f8b0:4864:20::131]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mQuxy-0005nq-9v for pgsql-hackers@postgresql.org; Thu, 16 Sep 2021 17:14:36 +0000 Received: by mail-il1-x131.google.com with SMTP id b8so7318430ilh.12 for ; Thu, 16 Sep 2021 10:14:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=k0pxhe9cZ3tre8qFmo7ZTYD20IRyiyEVNI+t8paC9zc=; b=Q1JWIh+CnuQGjJ09/3EeedEeLVkGn26BFb+cNjG72v14qPTmiykLmoB2/GFZUprGkx CaJZDzjAi5XQ5sTWbC4i2XYxjRwfphy+Tnpz1Nl5UpDVZ+pmlv67KzSh33GJRob/cfUY gEI2d9qvexJl0+LrlqTAZpDZTpBr7tbt1kK/7v7aBYsW0yS4iPyf+EHjhNKEMLyEVj7h ZH3FQkm31RTMZF/BjHDicKVFKruPNkhmfrcxUX2ONcNJMF+4kNrRsBnHZU4qpSWtsOx+ 0UPcoh0+TJFOFrs3Re7P6Y4JYXgIBKURE1y8Oov/N0/HWI+y16y/QkWVWpFJ13rlpfSV /aiw== 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:user-agent; bh=k0pxhe9cZ3tre8qFmo7ZTYD20IRyiyEVNI+t8paC9zc=; b=yHbwnMmEIr+pq70ohF0OwAbLhsX2//9pjtkYiJ/RKsqdYiIeIXX/aS3mUGOV1B7NXp TrF9pQDBpPsPTL9l5Iyn54eQAF/2xCFYmBFizn/AXSzwQQZgxPHUhVD96GihSRjzon9q UQgZPYlyMWhBwm7bLouArDY+vOHMsS1QmatrI9NYpb+kiOhWfacIw7OXCNsvn58/lc4o KdF/GT+983HLlwiWUv3aaNrg0NCmyeWfYEtB9XqYAcUr8i0RMgxEVLzhrpbcCgovv4u0 qN5m5HXPk6dPGH6+6d84j5cK7gmu5dKA7vSizL9U7BTdossYOvNOYfVjB0I2a/8lqmOa fG3g== X-Gm-Message-State: AOAM531f+LM2AsA15Tq/RZ60+wrRkogIiUY6eUys6gyZMSuReknzCFH3 jd8kcJhHaztmPwRrIOsIrkB59A== X-Google-Smtp-Source: ABdhPJxySvLxQg3i81xNplT3qtrb2vkjDEkqfGm4i1T6jqtLtvwAvn3xRfqwmoRXs6i8fcOXrrxbZA== X-Received: by 2002:a05:6e02:178d:: with SMTP id y13mr4810228ilu.266.1631812469373; Thu, 16 Sep 2021 10:14:29 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id s10sm2034934iom.40.2021.09.16.10.14.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Sep 2021 10:14:28 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id E3C7E800A1B; Thu, 16 Sep 2021 12:14:27 -0500 (CDT) Date: Thu, 16 Sep 2021 12:14:27 -0500 From: Justin Pryzby To: "Bossart, Nathan" Cc: Michael Paquier , Kyotaro Horiguchi , tgl@sss.pgh.pa.us, robertmhaas@gmail.com, masao.fujii@oss.nttdata.com, andres@anarazel.de, magnus@hagander.net, mark.dilger@enterprisedb.com, don@seiler.us, pgsql-hackers@postgresql.org Subject: Re: Estimating HugePages Requirements? Message-ID: <20210916171427.GR831@telsasoft.com> References: <506431.1631564654@sss.pgh.pa.us> <20210914.094936.565951707453489109.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk + * and the hugepage-related mmap flags to use into *mmap_flags. If huge pages + * is not supported, *hugepagesize and *mmap_flags will be set to 0. nitpick: *are* not supported, as you say elsewhere. + gettext_noop("Shows the number of huge pages needed for the main shared memory area."), Maybe this was already discussed, but "main" could be misleading. To me that sounds like there might be huge pages needed for something other than the "main" area and the reported value might turn out to be inadequate, (which is exactly the issue these patch are trying to address). In particular, this sounds like it's just going to report shared_buffers/huge_page_size (since shared buffers is usually the "main" use of shared memory) - rather than reporting the size of the entire shared memory in units of huge_pages. -- Justin