From mboxrd@z Thu Jan 1 00:00:00 1970 From: Iain Barker Subject: Re: Question about DPDK hugepage fd change Date: Wed, 6 Feb 2019 05:57:48 -0800 (PST) Message-ID: References: <631579E3-02F5-4E12-8BE6-DDAC0AE2E4A7@oracle.com> <549A6EB0-6E19-460D-9BE5-52AA40003AF0@intel.com> <345EDE69-C416-405F-B88C-04EE8384D20F@oracle.com> <896AF59A-4CCF-42FE-B2D7-160C69427DD2@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org, Edwin Leung , "Burakov, Anatoly" To: "Wiles, Keith" Return-path: Received: from aserp2130.oracle.com (aserp2130.oracle.com [141.146.126.79]) by dpdk.org (Postfix) with ESMTP id 364405B3C for ; Wed, 6 Feb 2019 14:57:57 +0100 (CET) In-Reply-To: <896AF59A-4CCF-42FE-B2D7-160C69427DD2@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > Can you use 1G hugepages instead of 2M pages or a combo of the two, not s= ure how dpdk handles having both in the system? Unfortunately, no. Some of our customer deployments are tenancies on KVM ho= sts and low-end appliances, which are not configurable by the end user to e= nable 1G huge pages. I think we are going to have to revert this patch set from our build, as I = don't see any other alternative for using DPDK 18 whilst remaining complian= t to the POSIX/glibc requirements.