From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 1E5A02B84 for ; Mon, 24 Apr 2017 11:40:05 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2017 02:40:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,244,1488873600"; d="scan'208";a="1160156017" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by fmsmga002.fm.intel.com with ESMTP; 24 Apr 2017 02:40:03 -0700 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.12]) by IRSMSX107.ger.corp.intel.com ([169.254.10.107]) with mapi id 14.03.0319.002; Mon, 24 Apr 2017 10:40:02 +0100 From: "Burakov, Anatoly" To: Alexey Kardashevskiy , Jonas Pfefferle1 CC: "dev@dpdk.org" , Adrian Schuepbach , Gowrishankar Muthukrishnan , "gowrishankar muthukrishnan" Thread-Topic: [dpdk-dev] [PATCH dpdk 5/5] RFC: vfio/ppc64/spapr: Use correct bus addresses for DMA map Thread-Index: AQHSudmpVdSwgNOxa0eRe//4KX0cXqHOPnyAgABSM4CAAI16gIAAVC+AgAEUSHKAA8Fh0A== Date: Mon, 24 Apr 2017 09:40:01 +0000 Message-ID: References: <20170420072402.38106-1-aik@ozlabs.ru> <20170420072402.38106-6-aik@ozlabs.ru> <12566b0a-8f9a-4040-a37d-2a106e49adcf@ozlabs.ru> <6e669e2b-2cfd-078d-b6b0-5c3819fad796@ozlabs.ru> <3e20a6f7-a1b7-4b13-5659-5afb827563ca@linux.vnet.ibm.com> <4977b4e8-e63a-0621-2375-89066d8de10a@ozlabs.ru> <2354a035-1c97-b9b4-9a15-d62a26d6d160@ozlabs.ru> <628bf1ee-5bb6-edc2-bc7e-2acc14533bd8@ozlabs.ru> In-Reply-To: <628bf1ee-5bb6-edc2-bc7e-2acc14533bd8@ozlabs.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOGFiNTNjYjEtZjRhYy00NWJmLTljNDItZTk0OWNiNWUyYzBmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6Imt6MEkzRk5aMFJnWVdzQzVNMTdDamdMQjdodXBUSGFXR2lDaDlucldIUmM9In0= dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH dpdk 5/5] RFC: vfio/ppc64/spapr: Use correct bus addresses for DMA map X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2017 09:40:06 -0000 Hi Alexey, > > DPDK tries to allocate all hugepages that are available to find the > > smallest amount of physically contiguous memory segments to cover the > > specified memory size. It then releases all those hugepages that it > > did not need not sure how this is related to orig=3D1/0 though. >=20 >=20 > No, it never does release a single page :-/ That is weird. As far as I can remember, when EAL initializes the pages, it checks if ther= e are any active locks on hugepage files for a given prefix (which presumab= ly you didn't set, so it uses a default "rte" prefix), and if there aren't,= it removes the hugepage files. That way, if the pages are still in use (e.= g. by a secondary process), they aren't removed, but if they aren't used, t= hen they are freed, and reserved back. That is, technically, DPDK never "frees" any pages (unless you don't supply= -m/--socket-mem switch, in which case it does free unused pages, but still= leaves used pages after exit), so after a DPDK process exit they're not cl= eaned up. However, whenever a primary DPDK process runs again, it is usuall= y able to clean them up and thus should be able to initialize again. Perhap= s something is preventing file removal from your hugetlbfs? Like, maybe a p= ermissions issue or something? Thanks, Anatoly