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 E2D3F5F5D for ; Thu, 7 Jun 2018 14:15:56 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2018 05:15:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,486,1520924400"; d="scan'208";a="62073389" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.101]) ([10.237.220.101]) by fmsmga001.fm.intel.com with ESMTP; 07 Jun 2018 05:15:53 -0700 To: Scott Branden , Srinath Mannam Cc: Ajit Khaparde , dev@dpdk.org References: <20180328045120.40098-1-ajit.khaparde@broadcom.com> <76474922-b2ad-dfcd-d62b-f605ec47d2e6@intel.com> <9f258ff5-8442-8d06-0deb-c6a7013a7ddf@broadcom.com> From: "Burakov, Anatoly" Message-ID: <203e6af6-bff9-ca34-9b61-9f29191196fa@intel.com> Date: Thu, 7 Jun 2018 13:15:49 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <9f258ff5-8442-8d06-0deb-c6a7013a7ddf@broadcom.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH] eal: add request to map reserved physical memory 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: Thu, 07 Jun 2018 12:15:58 -0000 On 06-Jun-18 1:18 AM, Scott Branden wrote: > Hi Anatoly, > > > On 18-04-27 09:49 AM, Burakov, Anatoly wrote: >> On 27-Apr-18 5:30 PM, Scott Branden wrote: >>> Hi Anatoly, >>> >>> We'd appreciate your input so we can come to a solution of supporting >>> the necessary memory allocations? >>> >> >> Hi Scott, >> >> I'm currently starting to work on a prototype that will be at least >> RFC'd (if not v1'd) during 18.08 timeframe. Basically, the idea is to >> create/destroy named malloc heaps dynamically, and allow user to >> request memory from them. You may then mmap() whatever you want and >> create a malloc heap out of it. >> >> Does that sound reasonable? >> > Is the plan still to have a patch for 18.08? > > Thanks, >  Scott > Hi Scott, The plan is still to submit an RFC during 18.08 timeframe, but since it will be an ABI break, it will only be integrated in the next (18.11) release. -- Thanks, Anatoly