netdev - Re: [PATCH v5 net-next 0/3] add DMA-sync-for-device capability to page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 20 Nov 2019 12:34:58 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     lorenzo@...nel.org
Cc:     netdev@...r.kernel.org, ilias.apalodimas@...aro.org,
        brouer@...hat.com, lorenzo.bianconi@...hat.com, mcroce@...hat.com,
        jonathan.lemon@...il.com
Subject: Re: [PATCH v5 net-next 0/3] add DMA-sync-for-device capability to
 page_pool API

From: Lorenzo Bianconi <lorenzo@...nel.org>
Date: Wed, 20 Nov 2019 16:54:16 +0200

> Introduce the possibility to sync DMA memory for device in the page_pool API.
> This feature allows to sync proper DMA size and not always full buffer
> (dma_sync_single_for_device can be very costly).
> Please note DMA-sync-for-CPU is still device driver responsibility.
> Relying on page_pool DMA sync mvneta driver improves XDP_DROP pps of
> about 170Kpps:
> 
> - XDP_DROP DMA sync managed by mvneta driver:	~420Kpps
> - XDP_DROP DMA sync managed by page_pool API:	~585Kpps
> 
> Do not change naming convention for the moment since the changes will hit other
> drivers as well. I will address it in another series.
 ...

Series applied, thanks.