[lkml]   [2018]   [Dec]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] avoid indirect calls for DMA direct mappings v2
On Fri,  7 Dec 2018 11:07:05 -0800
Christoph Hellwig <> wrote:

> Hi all,
> a while ago Jesper reported major performance regressions due to the
> spectre v2 mitigations in his XDP forwarding workloads. A large part
> of that is due to the DMA mapping API indirect calls.
> It turns out that the most common implementation of the DMA API is the
> direct mapping case, and now that we have merged almost all duplicate
> implementations of that into a single generic one is easily feasily to
> direct calls for this fast path.
> This series adds consolidate the DMA mapping code by merging the
> swiotlb case into the dma direct case, and then treats NULL dma_ops
> as an indicator that that we should directly call the direct mapping
> case. This recovers a large part of the retpoline induces XDP slowdown.
> This works is based on the dma-mapping tree, so you probably want to
> want this git tree for testing:
> git:// dma-direct-calls.2
> Gitweb:

You can add my:
Tested-by: Jesper Dangaard Brouer <>
Acked-by: Jesper Dangaard Brouer <>

I'm very happy that you work on this. And I've done micro-benchmark
testing of the patchset (and branch dma-direct-calls), which I've made
avail here:

My XDP performance is back, minus the BPF-indirect call, and
net_rx_action napi->poll, and net_device->ndo_xdp_xmit calls. I
verified that manually disabling retpoline for these remaining netstack
retpoline-calls restore the performance full (well minus 1.5 nanosec).

Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat

 \ /
  Last update: 2018-12-08 17:07    [W:0.199 / U:1.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site