From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 07D001C0F5 for ; Thu, 12 Apr 2018 16:36:03 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Apr 2018 07:35:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,442,1517904000"; d="scan'208";a="216082276" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.128]) ([10.237.220.128]) by orsmga005.jf.intel.com with ESMTP; 12 Apr 2018 07:35:54 -0700 To: Ajit Khaparde , dev@dpdk.org Cc: Srinath Mannam , Scott Branden References: <20180328045120.40098-1-ajit.khaparde@broadcom.com> From: "Burakov, Anatoly" Message-ID: Date: Thu, 12 Apr 2018 15:35:53 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180328045120.40098-1-ajit.khaparde@broadcom.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 12 Apr 2018 14:36:04 -0000 On 28-Mar-18 5:51 AM, Ajit Khaparde wrote: > From: Srinath Mannam > > Reserved physical memory is requested from kernel > and it will be mapped to user space. > This memory will be mapped to IOVA using VFIO. > And this memory will be provided to SPDK to allocate > NVMe CQs. > > Signed-off-by: Srinath Mannam > Signed-off-by: Scott Branden > Signed-off-by: Ajit Khaparde > --- Hi Srinath, I've seen this kind of approach implemented before to add additional memory types to DPDK (redefining "unused" socket id's to mean something else), and i don't like it. What would be better is to design a new API to support different memory types. Some groundwork for this was already laid for this release (switching to memseg lists), but more changes will be needed down the line. My ideal approach would be to have pluggable memory allocators. I've outlined some of my thoughts on this before [1], you're welcome to join/continue that discussion, and make sure whatever comes out of it is going to be useful for all of us :) I was planning to (attempt to) restart that discussion, and this seems like as good an opportunity to do that as any other. Now that the memory hotplug stuff is merged, i'll hopefully get more time prototyping. So, as it is, it's a NACK from me, but let's work together on something better :) [1] http://dpdk.org/ml/archives/dev/2018-February/090937.html -- Thanks, Anatoly