Re: [PATCH net-next 1/5] nfp: make use of the DMA_ATTR_SKIP_CPU_SYNC attr

2017-04-21 Thread David Miller
From: Alexander Duyck Date: Fri, 21 Apr 2017 08:07:45 -0700 > On Fri, Apr 21, 2017 at 7:20 AM, Jakub Kicinski > wrote: >> DMA unmap may destroy changes CPU made to the buffer. To make XDP >> run correctly on non-x86 platforms we should use the >> DMA_ATTR_SKIP_CPU_SYNC attribute. >> >> Thanks t

Re: [PATCH net-next 1/5] nfp: make use of the DMA_ATTR_SKIP_CPU_SYNC attr

2017-04-21 Thread Jakub Kicinski
On Fri, Apr 21, 2017 at 8:07 AM, Alexander Duyck wrote: > On Fri, Apr 21, 2017 at 7:20 AM, Jakub Kicinski > wrote: >> DMA unmap may destroy changes CPU made to the buffer. To make XDP >> run correctly on non-x86 platforms we should use the >> DMA_ATTR_SKIP_CPU_SYNC attribute. >> >> Thanks to usi

Re: [PATCH net-next 1/5] nfp: make use of the DMA_ATTR_SKIP_CPU_SYNC attr

2017-04-21 Thread Alexander Duyck
On Fri, Apr 21, 2017 at 7:20 AM, Jakub Kicinski wrote: > DMA unmap may destroy changes CPU made to the buffer. To make XDP > run correctly on non-x86 platforms we should use the > DMA_ATTR_SKIP_CPU_SYNC attribute. > > Thanks to using the attribute we can now push the sync operation to > the commo

[PATCH net-next 1/5] nfp: make use of the DMA_ATTR_SKIP_CPU_SYNC attr

2017-04-21 Thread Jakub Kicinski
DMA unmap may destroy changes CPU made to the buffer. To make XDP run correctly on non-x86 platforms we should use the DMA_ATTR_SKIP_CPU_SYNC attribute. Thanks to using the attribute we can now push the sync operation to the common code path from XDP handler. A little bit of variable name reshu