[dpdk-dev] [PATCH v3] i40: fix the VXLAN TSO issue

AN Tx checksum offload") Signed-off-by: Zhe Tao --- v2: edited the comments v3: added external IP offload flag when TSO is enabled for tunnelling packets app/test-pmd/csumonly.c | 29 + drivers/net/i40e/i40e_rxtx.c | 12 +--- lib/librte_mbuf/rte_mbu

[dpdk-dev] [PATCH v2] i40: fix the VXLAN TSO issue

On Thu, Jul 07, 2016 at 08:24:43PM +0800, Ananyev, Konstantin wrote: > > > > -Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Ananyev, Konstantin > > Sent: Thursday, July 07, 2016 11:51 AM > > To: Tao, Zhe; dev at dpdk.org > > Cc: Tao, Zhe; Wu, Jingjing > >

[dpdk-dev] [PATCH v2] i40: fix the VXLAN TSO issue

VXLAN Tx checksum offload") Signed-off-by: Zhe Tao --- V2: Edited some comments for mbuf structure and i40e driver. app/test-pmd/csumonly.c | 26 +++--- drivers/net/i40e/i40e_rxtx.c | 12 +--- lib/librte_mbuf/rte_mbuf.h | 16 +++- 3 files c

[dpdk-dev] [PATCH v15 2/2] i40e: add device args to enable a floating VEB

uires a NIC firmware version of 5.0 or greater. Signed-off-by: Zhe Tao --- doc/guides/nics/i40e.rst | 45 ++ doc/guides/rel_notes/release_16_07.rst | 8 ++ drivers/net/i40e/i40e_ethdev.c | 160 + drivers/net/i40e/i40e_ethdev.h

[dpdk-dev] [PATCH v15 1/2] i40e: add floating VEB support

oating VEB - even when the physical link on the NIC port is down. VFs VSIs connect either to the standard VEB/VEPA or to the floating VEB, they cannot connect to both of them. The PF, VMDQ and FD VSIs still connect to the normal VEB/VEPA. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethd

[dpdk-dev] [PATCH v15 0/2] i40e: add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W which newer than 5.0. Zhe Tao (2): i40e: add floating VEB support i40e

[dpdk-dev] [PATCH v14 2/2] i40e: add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. The floating VEB feature is only available for the FW version which newer than 5.0 (FW major version number > 5). Signed-off-by:

[dpdk-dev] [PATCH v14 1/2] i40e: support floating VEB config

ard VEB: 1. doesn't has a up link connection which means the traffic cannot go to outside world. 2. doesn't need to connect to the physical port which means when the physical link is down the floating VEB can still works fine. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethd

[dpdk-dev] [PATCH v14 0/2] i40e: add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W which newer than 5.0. Zhe Tao (2): i40e: support floating VEB config

[dpdk-dev] [PATCH v13 2/2] i40e: add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. The floating VEB feature is only available for the FW version which newer than 5.0 (FW major version number > 5). Signed-off-by:

[dpdk-dev] [PATCH v13 1/2] i40e: support floating VEB config

ard VEB: 1. doesn't has a up link connection which means the traffic cannot go to outside world. 2. doesn't need to connect to the physical port which means when the physical link is down the floating VEB can still works fine. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethd

[dpdk-dev] [PATCH v13 0/2] i40e: add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W which newer than 5.0. Zhe Tao (2): i40e: support floating VEB config

[dpdk-dev] [PATCH v12 1/2] i40e: support floating VEB config

On Fri, Jun 24, 2016 at 12:14:14PM +0100, Ferruh Yigit wrote: > Hi Zhe, > > On 6/24/2016 9:29 AM, Zhe Tao wrote: > > Add the new floating VEB related arguments option in the devarg. > > Using this parameter, all the applications can decide whether to use legacy > &g

[dpdk-dev] [PATCH v12 2/2] i40e: add floating VEB support in i40e

ing veb using "floating_veb_list". Like "-w 84:00.0,enable_floating_veb=1,floating_veb_list=1/3-4", means VF1, VF3, VF4 connect to the floating VEB, other VFs connect to the legacy VEB.The "/" is used for delimiter of the floating VEB list. Signed-off-by: Zhe Tao --- d

[dpdk-dev] [PATCH v12 1/2] i40e: support floating VEB config

the 802.1Qbg spec. But for floating VEB, it has two major difference. 1. doesn't has a up link connection which means the traffic cannot go to outside world. 2. doesn't need to connect to the physical port which means when the physical link is down the floating VEB can still works fine. Signe

[dpdk-dev] [PATCH v12 0/2] i40e: add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W which newer than 5.0. Zhe Tao (2): i40e: support floating VEB config

[dpdk-dev] [PATCH v11 3/3] i40e: add floating VEB extension support

loating VEB and one legacy VEB. VF can connect to floating VEB or legacy VEB according to the configuration. Signed-off-by: Zhe Tao --- doc/guides/nics/i40e.rst | 8 ++ drivers/net/i40e/i40e_ethdev.c | 56 -- drivers/net/i40e/i40e_ethdev.h | 1

[dpdk-dev] [PATCH v11 2/3] i40e: add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable for the FW version which newer than 5.0 (FW major version number > 5). Signed-off-by:

[dpdk-dev] [PATCH v11 1/3] i40e: support floating VEB config

he traffic cannot go to ouside world. 2. doesn't need to connect to the phsical port which means when the physical link is down the floating VEB can still works fine. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethdev.c | 44 ++ drivers/net/i40e/i40e_eth

[dpdk-dev] [PATCH v11 0/3] i40e: add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W which newer than 5.0. Zhe Tao (3): i40e: support floating VEB config

[dpdk-dev] [PATCH v3] i40e: fix olflags for vector Rx

: add vector Rx") Signed-off-by: Zhe Tao --- v2: Changed the comments according to the code change. v3: Fixed the issues reported by check-git-log.sh. drivers/net/i40e/i40e_rxtx_vec.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/net/i40e/i40e_rx

[dpdk-dev] [PATCH v11 0/3] i40e: add floating VEB support for i40e

On Tue, Jun 14, 2016 at 01:57:11PM +0800, Zhe Tao wrote: > This patch-set add the support for floating VEB in i40e. > All the VFs VSIs can decide whether to connect to the legacy VEB/VEPA or > the floating VEB. When connect to the floating VEB a new floating VEB is > created. Now all

[dpdk-dev] [PATCH v10 3/3] i40e: add floating VEB extension support

ne floating VEB and one legacy VEB. VF can connect to floating VEB or legacy VEB according to the configuration. Signed-off-by: Zhe Tao --- doc/guides/nics/i40e.rst | 8 ++ drivers/net/i40e/i40e_ethdev.c | 56 -- drivers/net/i40e/i40e_ethdev.h | 1

[dpdk-dev] [PATCH v10 2/3] i40e: add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable for the FW version which newer than 5.0 (FW major version number > 5). Signed-off-by:

[dpdk-dev] [PATCH v10 1/3] i40e: support floating VEB config

he traffic cannot go to ouside world. 2. doesn't need to connect to the phsical port which means when the physical link is down the floating VEB can still works fine. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethdev.c | 44 ++ drivers/net/i40e/i40

[dpdk-dev] [PATCH v10 0/3] i40e: add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W which newer than 5.0. Zhe Tao (3): Support floating VEB config Add

[dpdk-dev] [PATCH v9 3/3] i40e: add floating VEB extension support

ing VEB and one legacy VEB. VF can connect to floating VEB or legacy VEB according to the configuration. Signed-off-by: Zhe Tao --- doc/guides/nics/i40e.rst | 8 ++ drivers/net/i40e/i40e_ethdev.c | 56 -- drivers/net/i40e/i40e_ethdev.h | 1

[dpdk-dev] [PATCH v9 2/3] i40e: add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable for the FW version which newer than 5.0 (FW major version number > 5). Signed-off-by:

[dpdk-dev] [PATCH v9 1/3] i40e: support floating VEB config

he traffic cannot go to ouside world. 2. doesn't need to connect to the phsical port which means when the physical link is down the floating VEB can still works fine. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethdev.c | 44 ++ drivers/net/i40e/i40

[dpdk-dev] [PATCH v9 0/3] i40e: add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W which newer than 5.0. Zhe Tao (3): Support floating VEB config Add

[dpdk-dev] [PATCH v2] i40e: fix olflags for vector RX

) Signed-off-by: Zhe Tao --- v2: Changed the comments according to the code change. drivers/net/i40e/i40e_rxtx_vec.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/net/i40e/i40e_rxtx_vec.c b/drivers/net/i40e/i40e_rxtx_vec.c index eef80d9..dd113f3 100644

[dpdk-dev] [PATCH v4 8/8] i40e: implement device reset on VF

, and then release the locks. Signed-off-by: Zhe Tao --- doc/guides/rel_notes/release_16_07.rst | 5 ++ drivers/net/i40e/i40e_ethdev.h | 7 +- drivers/net/i40e/i40e_ethdev_vf.c | 152 - drivers/net/i40e/i40e_rxtx.c | 10 +++ drivers/net/i40e/i40e_rxtx.h

[dpdk-dev] [PATCH v4 7/8] i40e: RX/TX with lock on VF

Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path is chosen. Signed-off-by: Zhe Tao

[dpdk-dev] [PATCH v4 6/8] igb: implement device reset on VF

Implement the device reset function. 1, Add the fake RX/TX functions. 2, The reset function tries to stop RX/TX by replacing the RX/TX functions with the fake ones and getting the locks to make sure the regular RX/TX finished. 3, After the RX/TX stopped, reset the VF port, and then

[dpdk-dev] [PATCH v4 5/8] igb: RX/TX with lock on VF

Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path is chosen. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH v4 4/8] ixgbe: implement device reset on VF

Implement the device reset function. 1, Add the fake RX/TX functions. 2, The reset function tries to stop RX/TX by replacing the RX/TX functions with the fake ones and getting the locks to make sure the regular RX/TX finished. 3, After the RX/TX stopped, reset the VF port, and then

[dpdk-dev] [PATCH v4 3/8] ixgbe: RX/TX with lock on VF

Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path is chosen. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH v4 2/8] lib/librte_ether: defind RX/TX lock mode

-by: Wenzhuo Lu Signed-off-by: Zhe Tao --- lib/librte_ether/rte_ethdev.h | 62 +++ 1 file changed, 62 insertions(+) diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h index 74e895f..4efb5e9 100644 --- a/lib/librte_ether/rte_ethdev.h +++ b

[dpdk-dev] [PATCH v4 1/8] lib/librte_ether: support device reset

Add an API to reset the device. It's for VF device in this scenario, kernel PF + DPDK VF. When the PF port down/up, APP should call this API to reset VF port. Most likely, APP should call it in its management thread and guarantee the thread safe. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH v4 0/8] support reset of VF link

on VF igb: implement device reset on VF Zhe Tao (2): i40e: RX/TX with lock on VF i40e: implement device reset on VF v1: Added the implementation for the VF reset functionality. v2: Changed the i40e related operations during VF reset. v3: Resent the patches because of the mail sent

[dpdk-dev] [PATCH v3 8/8] i40e: implement device reset on VF

, and then release the locks. Signed-off-by: Zhe Tao --- app/test-pmd/config.c | 3 + doc/guides/rel_notes/release_16_07.rst | 5 ++ drivers/net/i40e/i40e_ethdev.h | 7 +- drivers/net/i40e/i40e_ethdev_vf.c | 152 - drivers/net/i40e/i40e_rxtx.c

[dpdk-dev] [PATCH v3 7/8] i40e: RX/TX with lock on VF

Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path is chosen. Signed-off-by: Zhe Tao

[dpdk-dev] [PATCH v3 6/8] igb: implement device reset on VF

Implement the device reset function. 1, Add the fake RX/TX functions. 2, The reset function tries to stop RX/TX by replacing the RX/TX functions with the fake ones and getting the locks to make sure the regular RX/TX finished. 3, After the RX/TX stopped, reset the VF port, and then

[dpdk-dev] [PATCH v3 5/8] igb: RX/TX with lock on VF

Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path is chosen. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH v3 4/8] ixgbe: implement device reset on VF

Implement the device reset function. 1, Add the fake RX/TX functions. 2, The reset function tries to stop RX/TX by replacing the RX/TX functions with the fake ones and getting the locks to make sure the regular RX/TX finished. 3, After the RX/TX stopped, reset the VF port, and then

[dpdk-dev] [PATCH v3 3/8] ixgbe: RX/TX with lock on VF

Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path is chosen. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH v3 2/8] lib/librte_ether: defind RX/TX lock mode

-by: Wenzhuo Lu Signed-off-by: Zhe Tao --- lib/librte_ether/rte_ethdev.h | 62 +++ 1 file changed, 62 insertions(+) diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h index 74e895f..4efb5e9 100644 --- a/lib/librte_ether/rte_ethdev.h +++ b

[dpdk-dev] [PATCH v3 1/8] lib/librte_ether: support device reset

Add an API to reset the device. It's for VF device in this scenario, kernel PF + DPDK VF. When the PF port down/up, APP should call this API to reset VF port. Most likely, APP should call it in its management thread and guarantee the thread safe. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH v3 0/8] support reset of VF link

on VF igb: implement device reset on VF Zhe Tao (2): i40e: RX/TX with lock on VF i40e: implement device reset on VF v1: Added the implementation for the VF reset functionality. v2: Changed the i40e related operations during VF reset. v3: Resent the patches because of the mail sent

[dpdk-dev] [PATCH v2 8/8] i40e: implement device reset on VF

From: "zhe.tao" Implement the device reset function. 1, Add the fake RX/TX functions. 2, The reset function tries to stop RX/TX by replacing the RX/TX functions with the fake ones and getting the locks to make sure the regular RX/TX finished. 3, After the RX/TX stopped,

[dpdk-dev] [PATCH v2 7/8] i40e: RX/TX with lock on VF

From: "zhe.tao" Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path is

[dpdk-dev] [PATCH v2 6/8] igb: implement device reset on VF

From: Wenzhuo Lu Implement the device reset function. 1, Add the fake RX/TX functions. 2, The reset function tries to stop RX/TX by replacing the RX/TX functions with the fake ones and getting the locks to make sure the regular RX/TX finished. 3, After the RX/TX

[dpdk-dev] [PATCH v2 5/8] igb: RX/TX with lock on VF

From: Wenzhuo Lu Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path

[dpdk-dev] [PATCH v2 4/8] ixgbe: implement device reset on VF

From: Wenzhuo Lu Implement the device reset function. 1, Add the fake RX/TX functions. 2, The reset function tries to stop RX/TX by replacing the RX/TX functions with the fake ones and getting the locks to make sure the regular RX/TX finished. 3, After the RX/TX

[dpdk-dev] [PATCH v2 3/8] ixgbe: RX/TX with lock on VF

From: Wenzhuo Lu Add RX/TX paths with lock for VF. It's used when the function of link reset on VF is needed. When the lock for RX/TX is added, the RX/TX can be stopped. Then we have a chance to reset the VF link. Please be aware there's performence drop if the lock path

[dpdk-dev] [PATCH v2 2/8] lib/librte_ether: defind RX/TX lock mode

global variable are impacted. Signed-off-by: Wenzhuo Lu Signed-off-by: Zhe Tao Signed-off-by: zhe.tao --- lib/librte_ether/rte_ethdev.h | 62 +++ 1 file changed, 62 insertions(+) diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h

[dpdk-dev] [PATCH v2 1/8] lib/librte_ether: support device reset

From: Wenzhuo Lu Add an API to reset the device. It's for VF device in this scenario, kernel PF + DPDK VF. When the PF port down/up, APP should call this API to reset VF port. Most likely, APP should call it in its management thread and guarantee the thread safe.

[dpdk-dev] [PATCH v2 0/8] support reset of VF link

From: "zhe.tao" If the PF link is down and up, VF link will not work accordingly. This patch set addes the support of VF link reset. So, when VF receices the messges of physical link down/up. APP can reset the VF link and let it recover. PS: This patch set is splitted from a

[dpdk-dev] [PATCH] i40e: fix flexible payload selection

I40E_PRTQF_FLX_PIT_DEST_OFF_SHIFT) & \ > I40E_PRTQF_FLX_PIT_DEST_OFF_MASK)) > > -- > 2.4.0 Acked-by: Zhe Tao

[dpdk-dev] [PATCH 0/2] NSH packet type support in i40e

| 3 +++ > doc/guides/rel_notes/release_16_07.rst | 2 ++ > drivers/net/i40e/i40e_rxtx.c | 27 +++ > lib/librte_mbuf/rte_mbuf.h | 7 +++ > 4 files changed, 39 insertions(+) > > -- > 2.4.0 Acked-by: Zhe Tao

[dpdk-dev] [PATCH v8 3/3] i40e: add floating VEB extension support

s floating veb using "floating_bitmap", every bit corresponding to one VF (e.g. bitn for VFn). Like "-w 84:00.0,enable_floating=1,floating_bitmap=1", means only the VF0 connect to the floating VEB, VF1 connect to the legacy VEB. Signed-off-by: Zhe Tao --- doc/guides/nics/i40

[dpdk-dev] [PATCH v8 2/3] i40e: Add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable in the specific version of FW. Signed-off-by: Zhe Tao --- doc/guides/nics/i40e.rst

[dpdk-dev] [PATCH v8 1/3] i40e: support floating VEB config

pplication will make sure the PMD will use the floating VEB feature for all the VFs created by this PF device. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethdev.c | 44 ++ drivers/net/i40e/i40e_ethdev.h | 6 ++ 2 files changed, 50 insertions(+)

[dpdk-dev] [PATCH v8 0/3] i40e: Add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W. Zhe Tao (3): Support floating VEB config Add floating VEB support

[dpdk-dev] [PATCH v1] i40e: fix olflags for vector RX

) Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_rxtx_vec.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net/i40e/i40e_rxtx_vec.c b/drivers/net/i40e/i40e_rxtx_vec.c index eef80d9..9f674bf 100644 --- a/drivers/net/i40e/i40e_rxtx_vec.c +++ b/drivers/net/i40e

[dpdk-dev] [PATCH v1] igu_uio: fix IOMMU domain issue

e page. Because all the DMA related alloc and map actions will cause the intel IOMMU driver to reload the SI domain to the context entry, that's why the kernel driver never meets such problem. Signed-off-by: Zhe Tao --- lib/librte_eal/linuxapp/igb_uio/igb_uio.c | 12 1 file chang

[dpdk-dev] [PATCH] i40e: support user unaware VF reset

Problem: Now the i40e VF PMD driver does not support reset event from PF. Customer want the user unaware VF reset feature in VF PMD driver, with this feature, the application doesn't need to concern about the VF reset procedure and all the application can work correctly when VF is doing the reset.

[dpdk-dev] [PATCH v2 0/3] improve i40e vpmd

erformance of vector PMD > i40e: simplify SSE packet length extraction code > > drivers/net/i40e/Makefile| 6 > drivers/net/i40e/i40e_rxtx_vec.c | 59 > ++-- > 2 files changed, 27 insertions(+), 38 deletions(-) > > -- > 2.5.5 Acked-by: Zhe Tao

[dpdk-dev] [PATCH] vhost: fix mem share between VM and host

this mem is not shared between VM and host. Signed-off-by: Zhe Tao --- lib/librte_vhost/vhost-net.h | 1 + lib/librte_vhost/vhost_user/virtio-net-user.c | 7 --- lib/librte_vhost/virtio-net.c | 29 ++- 3 files changed, 33 insertions

[dpdk-dev] [PATCH v4] i40e: fix TSO issue for tx function

to trigger the i40e_txd_enable_checksum. The right logic here is we enable csum offload for both ipv4 and ipv6 when TSO flag is set. Fixes: e3f0151f (i40e: enable Tx checksum only for offloaded packets) Signed-off-by: Zhe Tao --- v2: changed condition check for ipv6 TSO checksum offload use a more

[dpdk-dev] [PATCH v3] i40e: fix TSO issue for tx function

Issue: when using the following CLI in testpmd to enable ipv6 TSO feature (set --txqflags=0 in the testpmd command) set verbose 1 csum set ip hw 0 csum set udp hw 0 csum set tcp hw 0 csum set sctp hw 0 csum set outer-ip hw 0 csum

[dpdk-dev] [PATCH v2] i40e: fix ipv6 TSO issue for tx function

On Thu, Mar 24, 2016 at 03:00:14PM +, Bruce Richardson wrote: > On Wed, Mar 23, 2016 at 11:27:50AM +0800, Zhe Tao wrote: > > Issue: > > when using the following CLI in testpmd to enable ipv6 TSO feature > > = > > set verbose 1 > > csum set ip hw 0 &

[dpdk-dev] [PATCH 3/3 v7] i40e: Add global reset support for i40e

the packet buffers, doesn't reset the PE firmware, and doesn't bother the other PFs on the chip. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethdev.c | 35 ++- drivers/net/i40e/i40e_ethdev.h | 30 ++ 2 files changed, 64 insertions(+), 1

[dpdk-dev] [PATCH 2/3 v7] i40e: Add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable in the specific version of FW. Signed-off-by: Zhe Tao --- doc/guides/nics/i40e.rst

[dpdk-dev] [PATCH 1/3 v7] i40e: support floating VEB config

pplication will make sure the PMD will use the floating VEB feature for all the VFs created by this PF device. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethdev.c | 44 ++ drivers/net/i40e/i40e_ethdev.h | 6 ++ 2 files changed, 50 insertions(+)

[dpdk-dev] [PATCH 0/3 v7] i40e: Add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W. Zhe Tao (2): Support floating VEB config Add floating VEB support

[dpdk-dev] [PATCH 2/2 v6] i40e: Add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable in the specific version of FW. Signed-off-by: Zhe Tao --- doc/guides/nics/i40e.rst

[dpdk-dev] [PATCH 1/2 v6] i40e: support floating VEB config

pplication will make sure the PMD will use the floating VEB feature for all the VFs created by this PF device. Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_ethdev.c | 44 ++ drivers/net/i40e/i40e_ethdev.h | 6 ++ 2 files changed, 50 insertions(+)

[dpdk-dev] [PATCH 0/2 v6] i40e: Add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W. Zhe Tao (2): support floating VEB config Add floating VEB support

[dpdk-dev] [PATCH 1/2 v5] i40e: support floating VEB config

On Wed, Mar 23, 2016 at 01:51:09PM +0100, Thomas Monjalon wrote: > 2016-03-23 20:27, Zhe Tao: > > Add the new floating related argument option in the EAL. > > Using this parameter, all the samples can decide whether to use legacy > > VEB/VEPA > > or floating VEB. >

[dpdk-dev] [PATCH 2/2 v5] i40e: Add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable in the specific version of FW. Signed-off-by: Zhe Tao --- doc/guides/rel_notes

[dpdk-dev] [PATCH 1/2 v5] i40e: support floating VEB config

Add the new floating related argument option in the EAL. Using this parameter, all the samples can decide whether to use legacy VEB/VEPA or floating VEB. Even the floating argument is provided in the EAL, but this floating feature are only support for FVL so far. Signed-off-by: Zhe Tao --- doc

[dpdk-dev] [PATCH 0/2 v5] i40e: Add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W. Zhe Tao (2): support floating VEB config Add floating VEB support

[dpdk-dev] [PATCH v2] i40e: fix ipv6 TSO issue for tx function

, ipv4 need the header csum, but ipv6 doesn't need the csum. We need to use the i40e_txd_enable_checksum to set the ipv6 type flag into the data descriptor when the packets are for ipv6 TSO. Fixes: e3f0151f (i40e: enable Tx checksum only for offloaded packets) Signed-off-by: Zhe Tao --- v2: change

[dpdk-dev] [PATCH] i40e: fix ipv6 TSO issue for tx function

On Tue, Mar 22, 2016 at 09:38:55PM +0800, Ananyev, Konstantin wrote: > Hi, > > > -Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Zhe Tao > > Sent: Tuesday, March 22, 2016 1:14 PM > > To: dev at dpdk.org > > Cc: Tao, Zhe

[dpdk-dev] [PATCH] i40e: fix ipv6 TSO issue for tx function

, ipv4 need the header csum, but ipv6 doesn't need the csum. We need to use the i40e_txd_enable_checksum to set the ipv6 type flag into the data descriptor when the packets are for ipv6 TSO. Fixes: e3f0151f (i40e: enable Tx checksum only for offloaded packets) Signed-off-by: Zhe Tao --- drivers

[dpdk-dev] [PATCH v2] i40e: fix build issue for RX set function

only depends on a C variable, which will cause the inconsistency and lead to the build error which will tell us the bulk recv function is not defined. Fixes: 8e109464 (i40e: allow vector Rx and Tx usage) Signed-off-by: Zhe Tao --- V2: fix some characters issues in commit log drivers/net/i40e

[dpdk-dev] [PATCH] i40e: fix build issue for RX set function

only depends on a C variable, which will cause the inconsistency and lead to the build error which will tell us the bulk recv function is not defined. Fixes: 8e109464 (i40e: allow vector Rx and Tx usage) Signed-off-by: Zhe Tao --- drivers/net/i40e/i40e_rxtx.c | 8 1 file changed, 8

[dpdk-dev] [PATCH v3] ixgbe: fix ixgbevf RX/TX function assignment

function when secondary process call the init function for eth dev. Fixes: 46bc9d75 (ixgbe: fix multi-process support) Signed-off-by: Zhe Tao --- V2:added fixes line V3:changed fixes line drivers/net/ixgbe/ixgbe_ethdev.c | 17 +++-- 1 file changed, 15 insertions(+), 2 deletions

[dpdk-dev] [PATCH v3] i40e: add VEB switching support for i40e

: a virtual interface connect between the VEB/VEPA and virtual machine. VEPA: a virtual Ethernet port aggregator will upstream the packets from VSI to the LAN port. Signed-off-by: Zhe Tao --- v1: Add the VEB switching support. v2: Add the check for the FW version, which should larger than 5.0. Add

[dpdk-dev] [PATCH v3 0/2] i40evf: pf reset event report

+-- > lib/librte_ether/rte_ethdev.h | 1 + > 4 files changed, 301 insertions(+), 123 deletions(-) > > -- > 2.4.0 Acked-by: Zhe Tao

[dpdk-dev] [PATCH v2] ixgbe: fix ixgbevf RX/TX function assignment

function when secondary process call the init function for eth dev. Fixes: abf7275bbaa2918 (ixgbe: move to drivers/net/) V2:add fixes line Signed-off-by: Zhe Tao --- drivers/net/ixgbe/ixgbe_ethdev.c | 17 +++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/drivers

[dpdk-dev] [PATCH v2 0/2] add VF MAC address generation

40e/i40e_ethdev_vf.c | 14 +++--- > drivers/net/i40e/i40e_pf.c | 3 +++ > 4 files changed, 16 insertions(+), 7 deletions(-) > > -- > 2.5.0 Acked-by: Zhe Tao

[dpdk-dev] i40e & ixgbe xmit issue: txe->next_id

Hi all, I have a question about why we need the txe->next_id field in the i40e Tx function? >From the current implementation, all the txe is initialized and free >sequentially, so we don't need this "next_id" field in our TX function, and when we decide the "last_id" for txe, we assume the txe is

[dpdk-dev] [PATCH 2/2 v4] i40e: Add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Now the floating VEB feature is only avaiable in the specific version of FW. Signed-off-by: Zhe Tao --- doc/guides/rel_notes

[dpdk-dev] [PATCH 1/2 v4] i40e: support floating VEB config

Add the new floating related argument option in the EAL. Using this parameter, all the samples can decide whether to use legacy VEB/VEPA or floating VEB. Even the floating argument is provided in the EAL, but this floating feature are only support for FVL so far. Signed-off-by: Zhe Tao --- doc

[dpdk-dev] [PATCH 0/2 v4] i40e: Add floating VEB support for i40e

of them. The PF and VMDQ,FD VSIs connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. This floating VEB only take effects on the specific version F/W. Zhe Tao (2): support floating VEB config Add floating VEB support

[dpdk-dev] [PATCH v2] ethdev: fix byte order inconsistence between fdir flow and mask

ine.c b/app/test-pmd/cmdline.c > index 73298c9..13194c9 100644 > --- a/app/test-pmd/cmdline.c > +++ b/app/test-pmd/cmdline.c > @@ -8687,13 +8687,13 @@ cmd_flow_director_mask_parsed(void *parsed_result, > return; > } Acked-by: Zhe Tao

[dpdk-dev] [PATCH] ixgbe: fix ixgbevf RX/TX function assignment

function when secondary process call the init function for eth dev. Signed-off-by: Zhe Tao --- drivers/net/ixgbe/ixgbe_ethdev.c | 17 +++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c b/drivers/net/ixgbe/ixgbe_ethdev.c index 3e6fe86

[dpdk-dev] [PATCH 2/2 v3] i40e: Add floating VEB support in i40e

of them. The PF and VMDQ,FD VSIs still connect to the old legacy VEB/VEPA. All the VEB/VEPA concepts are not specific for FVL, they are defined in the 802.1Qbg spec. Signed-off-by: Zhe Tao --- doc/guides/rel_notes/release_16_04.rst | 2 + drivers/net/i40e/Makefile | 2 +- drivers

  1   2   >