[dpdk-dev] [PATCH v1 0/5] introduce iavf backend driver

This series introduces a net device driver called iavfbe which is working as datapath driver for emulated iavf type device. It provides basic function following Intel® Ethernet Adaptive Virtual Function specification, including recevice/transmit packets and virtchnl control messages handling. The d

[dpdk-dev] [PATCH v1 1/5] net/iavf_be: introduce iavf backend driver

Introduce driver for iavf backend vdev which is based on vfio-user protocol and emudev libs. Signed-off-by: Jingjing Wu Signed-off-by: Kun Qiu --- drivers/net/iavf_be/iavf_be.h| 40 drivers/net/iavf_be/iavf_be_ethdev.c | 330 +++ drivers/net/iavf_be/meson.b

[dpdk-dev] [PATCH v1 2/5] net/iavf_be: control queue enabling

1. Set up control rx/tx queues. 2. Emu device callback functions implemention. 3. Enabling recv/send msg through control queue. Signed-off-by: Jingjing Wu Signed-off-by: Chenbo Xia Signed-off-by: Xiuchun Lu --- drivers/net/iavf_be/iavf_be.h| 39 drivers/net/iavf_be/iavf_be_ethdev

[dpdk-dev] [PATCH v1 3/5] net/iavf_be: virtchnl messages process

1. Process virtchnl messages from Front End. 2. Ethdev ops implemention for queues setup. Signed-off-by: Jingjing Wu Signed-off-by: Xiuchun Lu --- drivers/net/iavf_be/iavf_be.h| 44 ++ drivers/net/iavf_be/iavf_be_ethdev.c | 335 ++- drivers/net/iavf_be/iavf_be_rxtx.c | 162 ++

[dpdk-dev] [PATCH v1 4/5] net/iavf_be: add Rx Tx burst support

Enable packets revcieve and transmit functions. Signed-off-by: Jingjing Wu Signed-off-by: Xiuchun Lu Signed-off-by: Miao Li --- drivers/net/iavf_be/iavf_be_ethdev.c | 3 + drivers/net/iavf_be/iavf_be_rxtx.c | 329 +++ drivers/net/iavf_be/iavf_be_rxtx.h | 60 +

[dpdk-dev] [PATCH v1 5/5] doc: new net PMD iavf_be

Signed-off-by: Jingjing Wu --- MAINTAINERS| 6 +++ doc/guides/nics/features/iavf_be.ini | 11 ++ doc/guides/nics/iavf_be.rst| 53 ++ doc/guides/nics/index.rst | 1 + doc/guides/rel_notes/release_21_02.rst | 6 ++

[dpdk-dev] [PATCH] ci: fix package installation in GitHub Actions

APT cache must be updated to avoid trying to install an unavailable version of a package. Fixes: 87009585e293 ("ci: hook to GitHub Actions") Signed-off-by: David Marchand --- I did not find a way for the update to be done by GHA itself, so adding an explicit step. The robot hits this issue on a

[dpdk-dev] [PATCH v1 0/2] introduce new iavf driver on vfio-user client

This series introduces a new net virtual device called iavf_client which is based on vfio-user client interface. Through vfio-user client interface, PCI liked device could be used similar as Intel® Ethernet Adaptive Virtual Function specification. The code to enable iavf_client mainly contains two

[dpdk-dev] [PATCH v1 1/2] common/iavf: emulated pci interfaces on vfio-user client

This patch implements Emulated pci interfaces on vfio-user client which is located in common/iavf/vfio_user/. Four main functions provided to upper layer (driver) to set up or talk to device: - client_vfio_user_setup - client_vfio_user_release - client_vfio_user_get_bar_addr - client_vfio_user_

[dpdk-dev] [PATCH v1 2/2] net/iavf: introduce iavf driver on vfio-user client

This patch add a new net driver based on vdev abstraction, i.e. iavf_client_ethdev.c. It is using common iavf functions to talk with Emulated pci interfaces based on vfio-user. -- | -- | | | iavf driver | |> (iavf_client_ethdev.c)

[dpdk-dev] [PATCH 0/6] net/bnxt: add support for Stingray2

Add support for 58818/Stingray2 chip. The new chip Stingray 2 belongs to the P5 generation. Some changes in the PMD are required to support this new chip. This patchset adds the necessary changes. Please apply. Kalesh AP (6): net/bnxt: add support for 58818 chip family net/bnxt: add new RX ch

[dpdk-dev] [PATCH 1/6] net/bnxt: add support for 58818 chip family

From: Kalesh AP The new chip (Stingray 2) is part of the P5 chip family with a number of changes: 1. Implement the epoch doorbell bit for 58818 chip. With the new doorbell infrastructure and the unbounded index logic, now set the epoch doorbell bit to support proper doorbell operation on t

[dpdk-dev] [PATCH 2/6] net/bnxt: add new RX checksum mode

From: Kalesh AP The 58818 chips support two different checksum modes. Host driver has to register with FW which checksum mode it prefers to use. DPDK driver want to use "cs_all_ok_mode=1". FW advertises the support of the different checksum modes on per VNIC basis in the HWRM_VNIC_QCAPS response.

[dpdk-dev] [PATCH 3/6] net/bnxt: modify VNIC accounting

From: Kalesh AP Modify VNIC accounting when enabling RFS on newer chips. Unlike legacy chips, newer chips don't need additional VNIC resources for ntuple filter. Fix the code accordingly so that we don't reserve and allocate additional VNICs on newer chips. Signed-off-by: Kalesh AP Reviewed-by:

[dpdk-dev] [PATCH 4/6] net/bnxt: add LRO support for SR2 chip

From: Kalesh AP Add the new chip specific TPA v2 logic to bnxt_tpa_start() to fully support TPA on the new chip. Signed-off-by: Kalesh AP Reviewed-by: Ajit Khaparde --- drivers/net/bnxt/bnxt_rxr.c | 72 +++-- drivers/net/bnxt/bnxt_rxr.h | 12 ++- 2 files ch

[dpdk-dev] [PATCH 5/6] net/bnxt: modify context memory allocation code

From: Kalesh AP Newer devices like SR2 may have chip backing store and do not require host backed memory allocation. In these cases, HWRM_FUNC_BACKING_STORE_QCAPS will return a zero entry size to indicate contexts for which the host should not allocate backing store. Selectively allocate contex

[dpdk-dev] [PATCH 6/6] net/bnxt: add Rx logic for 58818 chips

From: Kalesh AP 1. On the new 58818 chips, the RX completion is largely the same except for the new completion opcode and the stripped VLAN format and checksum status. Added bnxt_parse_csum_v2(), bnxt_parse_pkt_type_v2() and bnxt_rx_vlan_v2() to support the new RX completion logic. 2. Di