[dpdk-dev] [PATCH v3 00/68] Memory Hotplug for DPDK

Hemant Agrawal hemant.agrawal at nxp.com
Thu Apr 5 16:20:04 CEST 2018


HI Thomas,

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas at monjalon.net]
> Sent: Thursday, April 05, 2018 7:43 PM
> To: Shreyansh Jain <shreyansh.jain at nxp.com>
> Cc: Anatoly Burakov <anatoly.burakov at intel.com>; dev at dpdk.org;
> keith.wiles at intel.com; jianfeng.tan at intel.com; andras.kovacs at ericsson.com;
> laszlo.vadkeri at ericsson.com; benjamin.walker at intel.com;
> bruce.richardson at intel.com; konstantin.ananyev at intel.com;
> kuralamudhan.ramakrishnan at intel.com; louise.m.daly at intel.com;
> nelio.laranjeiro at 6wind.com; yskoh at mellanox.com; pepperjo at japf.ch;
> jerin.jacob at caviumnetworks.com; Hemant Agrawal
> <hemant.agrawal at nxp.com>; olivier.matz at 6wind.com;
> gowrishankar.m at 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




More information about the dev mailing list