From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hemant Agrawal Subject: Re: [PATCH v3 00/68] Memory Hotplug for DPDK Date: Fri, 6 Apr 2018 12:01:58 +0000 Message-ID: References: <49bcdac0-2631-361d-c454-088c5c70f6b1@nxp.com> <2771974.P4zNJljvph@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: Anatoly Burakov , "dev@dpdk.org" , "keith.wiles@intel.com" , "jianfeng.tan@intel.com" , "andras.kovacs@ericsson.com" , "laszlo.vadkeri@ericsson.com" , "benjamin.walker@intel.com" , "bruce.richardson@intel.com" , "konstantin.ananyev@intel.com" , "kuralamudhan.ramakrishnan@intel.com" , "louise.m.daly@intel.com" , "nelio.laranjeiro@6wind.com" , "yskoh@mellanox.com" , "pepperjo@japf.ch" , "jerin.jacob@caviumnetworks.com" , "olivier.matz@6wind.com" , "gowrishankar.m@li To: Hemant Agrawal , Thomas Monjalon , Shreyansh Jain Return-path: Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0058.outbound.protection.outlook.com [104.47.1.58]) by dpdk.org (Postfix) with ESMTP id C74681CF68 for ; Fri, 6 Apr 2018 14:02:00 +0200 (CEST) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Thomas > > -----Original Message----- > > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > Sent: Thursday, April 05, 2018 7:43 PM > > To: Shreyansh Jain > > Cc: Anatoly Burakov ; dev@dpdk.org; > > keith.wiles@intel.com; jianfeng.tan@intel.com; > > andras.kovacs@ericsson.com; laszlo.vadkeri@ericsson.com; > > benjamin.walker@intel.com; bruce.richardson@intel.com; > > konstantin.ananyev@intel.com; kuralamudhan.ramakrishnan@intel.com; > > louise.m.daly@intel.com; nelio.laranjeiro@6wind.com; > > yskoh@mellanox.com; pepperjo@japf.ch; jerin.jacob@caviumnetworks.com; > > Hemant Agrawal ; olivier.matz@6wind.com; > > gowrishankar.m@linux.vnet.ibm.com > > Subject: Re: [dpdk-dev] [PATCH v3 00/68] Memory Hotplug for DPDK > > Importance: High > > > > 05/04/2018 16:24, Shreyansh Jain: > > > Physical addressing cases for both, dpaa/dpaa2, depend heavily on > > > the fact that physical addressing was the base and was available in > > > sorted manner. This is reversed/negated with hotplugging support. > > > So, rework of both the drivers is required from this perspective. > > > There are some suggestions floated by Anatoly and internally, but > > > work still needs to be done. > > > It also impacts a lot of use-cases for virtualization (no-iommu). > > > > So what is your recommendation? > > Can you rework PA case in dpaa/dpaa2 drivers within 18.05 timeframe? > > > We will like 2-3 more days on this before we can ack/nack this patch. > We are working on priority on this. PA case rework is not a trivial chan= ge. The patch is good to go. However, we will be making changes in dpaa/dpaa2 d= rivers to fix the PA issues shortly (within 18.05 timeframe) Anatoly needs to take care of following: 1. Comment by Shreyansh on " Re: [dpdk-dev] [PATCH v3 50/68] eal: replace m= emzone array with fbarray" 2. I could not apply the patches cleanly on current master. Tested-by: Hemant Agrawal =20 > Regards, > Hemant >=20