From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3AB36A0547 for ; Wed, 29 Sep 2021 12:04:15 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B1D78410ED; Wed, 29 Sep 2021 12:04:14 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 61C7240E3C for ; Wed, 29 Sep 2021 12:04:13 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 0D2725C0200; Wed, 29 Sep 2021 06:04:13 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 29 Sep 2021 06:04:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= iFNBMEHusOmjhsX+RKJm+bpujAcCMkku0W31RwXm1o4=; b=Z3YQg6+TXa33lA0W QbE2pBGSgN62SUb95uF/8RCo+eh31Y7eXYn9bCGv2F9+DI2qtef8kHv50WbQ4Jvv 3qk7Zy59Zfb7PDI6WdlN8x1cWAighS8GtMBgOFumYWWclo0CEpxPG9R/saFl9WSK WtQJhNiuvxpP1KTY5WHu2OHCQvp3maw1ipBzEk0ntmuBD1fYjoGWh2tFWglVBGqA GNu7AqSObOQzjCmejD0R95/BNVoao0uNsp7wdx3PPOcwtt0xuNteukBDahAT9l7Y k388kmtsUkKlZEVATPtF60UwINrVYwwEpTK4zn3YcSG7dlIvAF58I8DSUO5YaxEG JvTN7A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=iFNBMEHusOmjhsX+RKJm+bpujAcCMkku0W31RwXm1 o4=; b=jCU659NAMK/l6RF1fGukfmk+9CqQx+vIK8jhYXkruPnb9ERnUOkdOd2zc aP0RvEmH8kYF99FIe1kkhuQpfvb1kv6JlwmBnsyqMOE8Er7RD4Vuh3Y1lEnuaTSi VtIDEs3zfKnL7vJFA8HbVq3r/pIXTMrpG7w8d7M395qBvcAy8PIbozzQe02isu4Y hadaWjNP5YZjPLPlwsxOa1YBFespNzj8tJZDoud/v1IInSLTJRxExwMZJYy0T1R/ lccq5iVJHizrSxoiynPz3LfBNuvsbI9BO6dX9v2gSc+7pl8G2wsFqLzfSRtkyU0w vyfsya+6hVnbRv/Xi9uk+8R7uCL5g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudekvddgvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpedugefgvdefudfftdefge elgffhueekgfffhfeujedtteeutdejueeiiedvffegheenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrd hnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 29 Sep 2021 06:04:11 -0400 (EDT) From: Thomas Monjalon To: Jiany Wu Cc: users@dpdk.org, anatoly.burakov@intel.com, bruce.richardson@intel.com, olivier.matz@6wind.com, dmitry.kozliuk@gmail.com, stephen@networkplumber.org, john.mcnamara@intel.com Subject: Re: [dpdk-users] can we reserve hugepage and not release Date: Wed, 29 Sep 2021 12:04:10 +0200 Message-ID: <3927535.NYFkNA2spg@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org 18/09/2021 04:37, Jiany Wu: > Hello, > > I met a scenario that, need to start and stop the container many times for > the hugepage. But after several times container start and stop, the > hugepage is not able to reserve. > Hugepage size is 2MB, and HW only support 2MB, can't support 1GB. > Is there anyway to make sure the hugepage is still kept continuous? Thanks > indeed. Interesting question. I think we need to address it in the DPDK documentation. Anatoly, Stephen, Bruce, any advice please?