Re: [dpdk-dev] [PATCH v2 6/6] examples/ioat: rename application to dmafwd

[Conor Walsh <conor.walsh@intel.com>]

> Since the APIs have been updated from rawdev to dmadev, the application
> should also be renamed to match. This patch also includes the documentation
> updates for the renaming.
>
> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
> ---

<snip>

> -The initialization of hardware device is done by ``rte_rawdev_configure()``
> -function using ``rte_rawdev_info`` struct. After configuration the device is
> -started using ``rte_rawdev_start()`` function. Each of the above operations
> -is done in ``configure_rawdev_queue()``.
> +The initialization of hardware device is done by ``rte_dmadev_configure()`` and
> +``rte_dmadev_vchan_setup()`` functions using the ``rte_dmadev_conf`` and
> +``rte_dmadev_vchan_conf`` structs. After configuration the device is started
> +using ``rte_dmadev_start()`` function. Each of the above operations is done in
> +``configure_dmadev_queue()``.

These function names need to be updated for dmadev v22.

<snip>

>   The packets are received in burst mode using ``rte_eth_rx_burst()``
>   function. When using hardware copy mode the packets are enqueued in
> -copying device's buffer using ``ioat_enqueue_packets()`` which calls
> -``rte_ioat_enqueue_copy()``. When all received packets are in the
> -buffer the copy operations are started by calling ``rte_ioat_perform_ops()``.
> -Function ``rte_ioat_enqueue_copy()`` operates on physical address of
> +copying device's buffer using ``dma_enqueue_packets()`` which calls
> +``rte_dmadev_copy()``. When all received packets are in the
> +buffer the copy operations are started by calling ``rte_dmadev_submit()``.
> +Function ``rte_dmadev_copy()`` operates on physical address of
>   the packet. Structure ``rte_mbuf`` contains only physical address to
>   start of the data buffer (``buf_iova``). Thus the address is adjusted
>   by ``addr_offset`` value in order to get the address of ``rearm_data``

These function names need to be updated for dmadev v22.

Reviewed-by: Conor Walsh <conor.walsh@intel.com>