On 12/13/2016 1:54 PM, Ferruh Yigit wrote:

On 12/12/2016 2:38 PM, Keith Wiles wrote:

quoted

The PMD allows for DPDK and the host to communicate using a raw
device interface on the host and in the DPDK application. The device
created is a Tap device with a L2 packet header.

v12- Fixup minor changes for driver_name and version number
v11- Add the tap.rst to the nic/index.rst file
v10- Change the string name used to allow for multiple devices.
v9 - Fix up the docs to use correct syntax
v8 - Fix issue with tap_tx_queue_setup() not return zero on success.
v7 - Reword the comment in common_base and fix the data->name issue
v6 - fixed the checkpatch issues
v5 - merge in changes from list review see related emails
     fixed many minor edits
v4 - merge with latest driver changes
v3 - fix includes by removing ifdef for other type besides Linux
     Fix the copyright notice in the Makefile
v2 - merge all of the patches into one patch
     Fix a typo on naming the tap device
     Update the maintainers list

Signed-off-by: Keith Wiles <redacted>
---

    Reviewed-by: Ferruh Yigit [off-list ref]
    Tested-by: Aws Ismail [off-list ref]
    Tested-by: Vasily Philipov [off-list ref]

Applied to dpdk-next-net/master, thanks.

Hi Keith,

test-report [1] shows build error [2] for the PMD, I guess there is a
kernel version dependency, FYI.

Issue has been caught after integration.


[1]
http://dpdk.org/ml/archives/test-report/2017-January/009616.html


[2]
DPDK/drivers/net/tap/rte_eth_tap.c: In function ‘tun_alloc’:
DPDK/drivers/net/tap/rte_eth_tap.c:143:19: error: ‘IFF_MULTI_QUEUE’
undeclared (first use in this function)
compilation terminated due to -Wfatal-errors.