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 071F5326B for ; Mon, 7 Aug 2017 15:21:36 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Aug 2017 06:21:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,338,1498546800"; d="scan'208";a="1000928477" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga003.jf.intel.com with ESMTP; 07 Aug 2017 06:21:31 -0700 Received: from fmsmsx112.amr.corp.intel.com (10.18.116.6) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 7 Aug 2017 06:21:31 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.214]) by FMSMSX112.amr.corp.intel.com ([169.254.5.69]) with mapi id 14.03.0319.002; Mon, 7 Aug 2017 06:21:30 -0700 From: "Wiles, Keith" To: Stephen Hemminger CC: Kevin Wilson , "users@dpdk.org" Thread-Topic: [dpdk-users] Hugepage size on x86 architectures: Thread-Index: AQHTDp9AtfgSf/RTeUCljwMk5iiyfqJ4RPOAgAETT4A= Date: Mon, 7 Aug 2017 13:21:30 +0000 Message-ID: <0610CAE8-A7BD-476F-A70C-9BF33A09015D@intel.com> References: <20170806135607.1de07783@xeon-e3> In-Reply-To: <20170806135607.1de07783@xeon-e3> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.230.19] Content-Type: text/plain; charset="us-ascii" Content-ID: <998A9086DD215840B21F754B889E5735@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Hugepage size on x86 architectures: X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2017 13:21:38 -0000 > On Aug 6, 2017, at 3:56 PM, Stephen Hemminger wrote: >=20 > On Sun, 6 Aug 2017 13:31:48 +0300 > Kevin Wilson wrote: >=20 >> Is it possible to use in DPDK other hugepage size than 2MB and 1GB (in >> order to benchmark performance) >> on x86 architectures)? At this point we only have 4K, 2M and 1G, 4K is the normal page size and no= t strictly a huge page :-) The hardware needs to be able to support hugepages and the Linux kernel. Ru= nning without huge pages is one option you can select from the command line= . >=20 > I think this is a CPU hardware restriction. Regards, Keith