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 1nXzGN-0006Dg-3i for pgsql-bugs@arkaria.postgresql.org; Sat, 26 Mar 2022 05:46:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nXzGK-0005z0-H0 for pgsql-bugs@arkaria.postgresql.org; Sat, 26 Mar 2022 05:46:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nXzGK-0005yq-8S for pgsql-bugs@lists.postgresql.org; Sat, 26 Mar 2022 05:46:56 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nXzGH-0002LY-Pw for pgsql-bugs@lists.postgresql.org; Sat, 26 Mar 2022 05:46:55 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id D52D93200A6A; Sat, 26 Mar 2022 01:46:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sat, 26 Mar 2022 01:46:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=uen0snSmefAizAo8elQyYjoByoZ99Stg7byP/9 ORhV0=; b=sJTZn39+tvgVNDCWhTm9j5j4e5BebI7V2WkqXPHzMfZxPHjVY1tP02 wEAFexuzvIrerq/Zd/OO7v6UAqa3b0jCHibwE/o4USWwgWZPqlVlyK3YXmA1fB5v nYdoHAETIPwZnfL7hX63A3Ks1U1BMxo1TwOeEpm58wXJKg2Pp8oxpcse6EBTSm2D GVZ6H+lHfCqub/6lTDSu2P/UTWIg2HTN9tCXlcCObOAi4x8LA10z9ZHuDVT5jNc0 mm4rxzVXqvncxh/kudyRAAtqX1EcwVOZwAwzBGPCds42UHyLYoZlQTo456SvLW2j /xIDGZqBixTjcdQnf0VZpPWX1dA6MGcA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=uen0snSmefAizAo8e lQyYjoByoZ99Stg7byP/9ORhV0=; b=JMTvAcRwZow9d0T6sKEvBOHVBmAJOeD1+ JMhHX38p7WLvrt8QXq8KdMK7uO4WOtHTH67wnRuMD6Uv6q20fnogkxFzXw5RzMdv n5o80idf+hp3mPE1Eu2RTOriGHHPTfBBSAfNsqt/uUI0h+io6Il0FDN2Dhr/pUQQ suAKK0fjy3mrhnv8Er7Bv1FZwHKbFCSXxQsf8Qj8L/XBYdEEtI1Qc8PqQqXYo+4a vvVcAplsqFT9R5VUfmA/AQwXhC6cr/eb9DRK/n5Pfi6Yy33dPw6nevPbCxxG0Pnp 5qZaauC5EBrM7Lp3PpUCMuBumM8/RCfbEeSZBIJVXRDE5MVNURTng== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudehvddgkeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdljedtmdenucfjughrpeffhf fvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhu ihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrh hnpedvgeduuefhtdeuleettdevjeehheeiveeuieegleetgeeljeelieeuieehgeevhfen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthh grvghlsehprghquhhivghrrdighiii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 26 Mar 2022 01:46:47 -0400 (EDT) Date: Sat, 26 Mar 2022 14:46:45 +0900 From: Michael Paquier To: okano.naoki@jp.fujitsu.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. Message-ID: References: <17448-0a96583a67edb1f7@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ComGMTp8hpdAgrqm" Content-Disposition: inline In-Reply-To: <17448-0a96583a67edb1f7@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --ComGMTp8hpdAgrqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 25, 2022 at 07:52:57AM +0000, PG Bug reporting form wrote: > On this page (*) says that in Windows 10, version 1703 and later OS > versions, =20 > you must specify the FILE_MAP_LARGE_PAGES flag with the MapViewOfFile > function=20 > to map large pages. >=20 > I think it seems to be the cause that MapViewOfFile() in > src/backend/port/win32_shmem.c=20 > does not specify FILE_MAP_LARGE_PAGES flag. Hmm. Okay. A patch would be straight-forward, as we could just assign the optional flag in a separate variable at the beginning of PGSharedMemoryCreate(), similarly to flProtect when we find out that large pages can be used, then pass it down to MapViewOfFileEx(). I don't have a Windows 10 machine as recent as that at hand, though.. Perhaps the CI uses Windows machines that would allow to test and check that, with some logs magically added to debug things. -- Michael --ComGMTp8hpdAgrqm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmI+qMUACgkQnvQgOdby QH1qIRAAhMr3o+6eqxKHXFrevSUJT1ZHERKab0F37Q944/KpsGWIcpbyG9J9DhsZ Cy0V4ZFlZEsizl+nHb+UP0mU8v4QoSTiPv+ez7GG91Ckbp6RQRT4RhjSDKzB0Apd ej24aB8yrMa8qsMD2tU9IIliaJugtA7zf5WTEceHh8bwCYkVXbul1F/ZULS4l9QD MVh92/cvJisTfHWLeh7fSYtgEZxdbEgzNUsXlgkr2j7SOB4MnYDS4+cbJF/9k5DV vsU790NgjGDWZ3EwJLQZlrwert8wuvUS634l2eWOi7k/ZMrC1G4H2qU/7wVadNP8 usHesasQFNU0kQVKu7E5j5rHzo8rpjM19hKzedDEiw9VyUQmUVnkwPtUo32JZ4LQ a47Co7Url1oD646pZ5A8CsJMihLuzT+ijMOzCJgvQUxM9Ab88OFxXI1JRGP7fGaA HqmhaEA6aYEOEHHCDuGi3cV7cfX6hsmpwlea+zuSPv2KZ0Id52vx471ZSh4cwnGB rTTf0F/a2IMihCzq291ZJ1KcKVcLjvvVHWQzBacmQOiau02XwlYjlyXU1IWosV3f pJ3H0MBZJfgXgqqwaadTPJpdSBhdbn2rsRXyM7LlgGhqfwMaLgZZAtqvL2g6CJRR pcRsEwHhHd6MUF/fBsJHU/NJ20XoXm6aDEQoh4a4qc4lXwY05cQ= =Zg3a -----END PGP SIGNATURE----- --ComGMTp8hpdAgrqm--