[dpdk-dev] [PATCH v5 0/9] raw/ioat: driver for Intel QuickData Technology

[Ferruh Yigit]

On 7/2/2019 3:12 PM, Bruce Richardson wrote:
> This patch series adds support for the Intel QuickData Technology
> device, part of the Intel I/O Acceleration Technology (Intel I/OAT). It
> is a raw device for allowing hardware DMA i.e. data copies in hardware.
> 
> Performing the copies in hardware can provide performance improvements
> for applications where the average copy size is reasonably large, e.g.
> 1k packets. For smaller packets, e.g. 64-256 bytes, offloading the copy
> may reduce performance due to the overhead of using hardware.
> 
> V5:
>  * updated doxygen comment for internal rawdev pmd API
> 
> V4:
>  * changed memory management to use contiguous memzones instead of
>    malloc memory
>  * added missing device ids for BDX platforms
>  * other misc cleanup following review (see individual patches logs)
> 
> V3:
>  * removed DPDK-specific structure for the descriptor format and reused
>    the structure in the imported file rte_ioat_spec.h
> 
> V2:
> * moved tests to rawdev selftest function
> * some checkpatch and other small cleanups
> * added extra documentation details on supported hardware
> * aligned the changes to dpdk-devbind with the changes in the NTB set
>   for consistency
> 
> 
> Bruce Richardson (9):
>   rawdev: allow devices to skip extra memory allocation
>   raw/ioat: add initial support for ioat rawdev driver
>   usertools/dpdk-devbind.py: add support for IOAT devices
>   raw/ioat: add register definition file
>   raw/ioat: create device on probe and destroy on release
>   raw/ioat: add device info function
>   raw/ioat: add configure, start and stop functions
>   raw/ioat: add statistics functions
>   raw/ioat: add local API to perform copies


Hi Bruce, Thomas,

Getting following build error with icc, both for 32-bit & 64-bit:

.../dpdk/drivers/raw/ioat/ioat_rawdev_test.c(28): (col. 9) error #13203: No EMMS
instruction before call to function