Re: [net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-28 Thread David Miller
From: Alexander Duyck Date: Fri, 28 Oct 2016 08:48:01 -0700 > So the feedback for this set has been mostly just a few "Acked-by"s, > and it looks like the series was marked as "Not Applicable" in > patchwork. I was wondering what the correct merge strategy for this >

Re: [net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-28 Thread David Miller
From: Alexander Duyck Date: Fri, 28 Oct 2016 08:48:01 -0700 > So the feedback for this set has been mostly just a few "Acked-by"s, > and it looks like the series was marked as "Not Applicable" in > patchwork. I was wondering what the correct merge strategy for this > patch set should be going

Re: [net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-28 Thread Alexander Duyck
On Tue, Oct 25, 2016 at 8:36 AM, Alexander Duyck wrote: > The first 22 patches in the set add support for the DMA attribute > DMA_ATTR_SKIP_CPU_SYNC on multiple platforms/architectures. This is needed > so that we can flag the calls to dma_map/unmap_page so that we

Re: [net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-28 Thread Alexander Duyck
On Tue, Oct 25, 2016 at 8:36 AM, Alexander Duyck wrote: > The first 22 patches in the set add support for the DMA attribute > DMA_ATTR_SKIP_CPU_SYNC on multiple platforms/architectures. This is needed > so that we can flag the calls to dma_map/unmap_page so that we do not > invalidate cache

Re: [net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-26 Thread Jesper Dangaard Brouer
On Tue, 25 Oct 2016 11:36:48 -0400 Alexander Duyck wrote: > The first 22 patches in the set add support for the DMA attribute > DMA_ATTR_SKIP_CPU_SYNC on multiple platforms/architectures. This is needed > so that we can flag the calls to dma_map/unmap_page so that

Re: [net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-26 Thread Jesper Dangaard Brouer
On Tue, 25 Oct 2016 11:36:48 -0400 Alexander Duyck wrote: > The first 22 patches in the set add support for the DMA attribute > DMA_ATTR_SKIP_CPU_SYNC on multiple platforms/architectures. This is needed > so that we can flag the calls to dma_map/unmap_page so that we do not > invalidate cache

[net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-25 Thread Alexander Duyck
The first 22 patches in the set add support for the DMA attribute DMA_ATTR_SKIP_CPU_SYNC on multiple platforms/architectures. This is needed so that we can flag the calls to dma_map/unmap_page so that we do not invalidate cache lines that do not currently belong to the device. Instead we have to

[net-next PATCH 00/27] Add support for DMA writable pages being writable by the network stack

2016-10-25 Thread Alexander Duyck
The first 22 patches in the set add support for the DMA attribute DMA_ATTR_SKIP_CPU_SYNC on multiple platforms/architectures. This is needed so that we can flag the calls to dma_map/unmap_page so that we do not invalidate cache lines that do not currently belong to the device. Instead we have to