From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 4DE8530D for ; Tue, 1 Jul 2014 10:56:27 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 01 Jul 2014 01:56:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,580,1400050800"; d="scan'208";a="563452341" Received: from fmsmsx108.amr.corp.intel.com ([10.19.9.228]) by fmsmga002.fm.intel.com with ESMTP; 01 Jul 2014 01:56:46 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by FMSMSX108.amr.corp.intel.com (10.19.9.228) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 1 Jul 2014 01:56:46 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx156.amr.corp.intel.com (10.18.116.74) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 1 Jul 2014 01:56:45 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.81]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.209]) with mapi id 14.03.0123.003; Tue, 1 Jul 2014 16:56:44 +0800 From: "Liu, Jijiang" To: Matt Laswell Thread-Topic: [dpdk-dev] Ability to/impact of running with smaller page sizes Thread-Index: AQHPlLTY3TIA0vBd7UiPydAK8q1+9JuJymKAgAEZ/bA= Date: Tue, 1 Jul 2014 08:56:43 +0000 Message-ID: <1ED644BD7E0A5F4091CF203DAFB8E4CC01D3D561@SHSMSX101.ccr.corp.intel.com> References: <20140630234229.GA19646@plxv1142.pdx.intel.com> In-Reply-To: <20140630234229.GA19646@plxv1142.pdx.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Ability to/impact of running with smaller page sizes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2014 08:56:27 -0000 Hi Matt, On Mon, Jun 30, 2014 at 05:43:39PM -0500, Matt Laswell wrote: > Hey Folks, >=20 > In my application, I'm seeing some design considerations in a project=20 > I'm working on that push me towards the use of smaller memory page=20 > sizes. I'm curious - is it possible in practical terms to run DPDK witho= ut hugepages? > If so, does anybody have any practical experience (or a=20 > back-of-the-envelop estimate) of how badly such a configuration would=20 > hurt performance? For sake of argument, assume that virtually all of=20 > the memory being used is in pre-allocated mempools (e.g lots of=20 > rte_mempool_create(), very little rte_malloc(). >=20 There is an case to run DPDK without hugepages in DPDK source codes, which = is DPDK supports Xen Dom0. for this, we developed a dom0_mm driver.=20 Except for Xen Dom0, it is impossible to run DPDK without hugepages without= any changes at memory initialization phase, but current rte_memzone_reserv= e_bounded() and=20 rte_mempool_xmem_create() implemention have already support non-hugepage u= sage in DPDK. =20 =20 =20 Thanks, Jeff