Hi Thomas > > -----Original Message----- > > From: Thomas Monjalon [mailto:[email protected]] > > Sent: Thursday, April 05, 2018 7:43 PM > > To: Shreyansh Jain <[email protected]> > > Cc: Anatoly Burakov <[email protected]>; [email protected]; > > [email protected]; [email protected]; > > [email protected]; [email protected]; > > [email protected]; [email protected]; > > [email protected]; [email protected]; > > [email protected]; [email protected]; > > [email protected]; [email protected]; [email protected]; > > Hemant Agrawal <[email protected]>; [email protected]; > > [email protected] > > 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.
The patch is good to go. However, we will be making changes in dpaa/dpaa2 drivers 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 memzone array with fbarray" 2. I could not apply the patches cleanly on current master. Tested-by: Hemant Agrawal <[email protected]> > Regards, > Hemant >
