HI Thomas, > -----Original Message----- > From: Thomas Monjalon [mailto:tho...@monjalon.net] > Sent: Thursday, April 05, 2018 7:43 PM > To: Shreyansh Jain <shreyansh.j...@nxp.com> > Cc: Anatoly Burakov <anatoly.bura...@intel.com>; dev@dpdk.org; > keith.wi...@intel.com; jianfeng....@intel.com; andras.kov...@ericsson.com; > laszlo.vadk...@ericsson.com; benjamin.wal...@intel.com; > bruce.richard...@intel.com; konstantin.anan...@intel.com; > kuralamudhan.ramakrish...@intel.com; louise.m.d...@intel.com; > nelio.laranje...@6wind.com; ys...@mellanox.com; peppe...@japf.ch; > jerin.ja...@caviumnetworks.com; Hemant Agrawal > <hemant.agra...@nxp.com>; olivier.m...@6wind.com; > gowrishanka...@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 change.
Regards, Hemant
