On 06/03/17 12:57, Sunil Kovvuri wrote:
>>>
>>> We are seeing a 0.75Mpps drop with IP forwarding rate due to that.
>>> Hence I have restricted calling DMA interfaces to only when IOMMU is
>>> enabled.
>>
>> What's 0.07Mpps as a percentage of baseline? On a correctly configured
>> coherent arm64 system, in the absence of an IOMMU, dma_map_*() is
>> essentially just virt_to_phys() behind a function call or two, so I'd be
>> interested to know where any non-trivial overhead might be coming from.
>
> It's a 5% drop and yes device is configured as coherent.
> And the drop is due to additional function calls.
OK, interesting - sounds like there's potential for some optimisation
there as well. AFAICS the callchain goes:
dma_map_single_attrs (inline)
- ops->map_page (__swiotlb_map_page)
- swiotlb_map_page
- phys_to_dma (inline)
- dma_capable (inline)
Do you happen to have a breakdown of where the time goes? If it's mostly
just in the indirect branch our options are limited (I'm guessing
ThunderX doesn't have a particularly fancy branch predictor, if it's not
even got a data prefetcher), but if it's in the SWIOTLB code then
there's certainly room for improvement (which will hopefully tie in with
some DMA ops work I'm planning to do soon anyway).
Thanks,
Robin.
>
> Thanks,
> Sunil.
>
