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

Burakov, Anatoly anatoly.burakov at intel.com
Fri Apr 6 14:55:28 CEST 2018


On 06-Apr-18 1:01 PM, Hemant Agrawal wrote:
> 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.
> 
> 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)

That's great to hear!

> 
> 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"

Yes, that is already fixed in both github and upcoming v4.

> 2. I could not apply the patches cleanly on current master.

The patchset has dependencies, listed in the cover letter. I'll rebase 
on latest master before sending v4 just in case.

> 
> Tested-by: Hemant Agrawal <hemant.agrawal at nxp.com>
>   
>> Regards,
>> Hemant
>>
> 
> 


-- 
Thanks,
Anatoly


More information about the dev mailing list