Re: [PATCH v8 17/45] powerpc/powernv/ioda1: Improve DMA32 segment track

2016-04-19 Thread Alexey Kardashevskiy
On 04/20/2016 10:49 AM, Gavin Shan wrote: On Tue, Apr 19, 2016 at 11:50:10AM +1000, Alexey Kardashevskiy wrote: On 02/17/2016 02:44 PM, Gavin Shan wrote: In current implementation, the DMA32 segments required by one specific PE isn't calculated with the information hold in the PE

Re: [PATCH v8 17/45] powerpc/powernv/ioda1: Improve DMA32 segment track

2016-04-19 Thread Gavin Shan
On Tue, Apr 19, 2016 at 11:50:10AM +1000, Alexey Kardashevskiy wrote: >On 02/17/2016 02:44 PM, Gavin Shan wrote: >>In current implementation, the DMA32 segments required by one specific >>PE isn't calculated with the information hold in the PE independently. >>It conflicts with the PCI hotplug

Re: [PATCH v8 17/45] powerpc/powernv/ioda1: Improve DMA32 segment track

2016-04-18 Thread Alexey Kardashevskiy
On 02/17/2016 02:44 PM, Gavin Shan wrote: In current implementation, the DMA32 segments required by one specific PE isn't calculated with the information hold in the PE independently. It conflicts with the PCI hotplug design: PE centralized, meaning the PE's DMA32 segments should be calculated

[PATCH v8 17/45] powerpc/powernv/ioda1: Improve DMA32 segment track

2016-02-16 Thread Gavin Shan
In current implementation, the DMA32 segments required by one specific PE isn't calculated with the information hold in the PE independently. It conflicts with the PCI hotplug design: PE centralized, meaning the PE's DMA32 segments should be calculated from the information hold in the PE