Re: [dpdk-dev] [PATCH v2] examples/tep_term: deprecate this example

2020-10-20 Thread Li, Xiaoyun
OK. > -Original Message- > From: Thomas Monjalon > Sent: Tuesday, October 20, 2020 19:43 > To: Li, Xiaoyun > Cc: Yigit, Ferruh ; dev@dpdk.org; > arybche...@solarflare.com; david.march...@redhat.com > Subject: Re: [dpdk-dev] [PATCH v2] examples/tep_term: deprecate th

Re: [dpdk-dev] [PATCH v2] examples/tep_term: deprecate this example

2020-10-20 Thread Thomas Monjalon
20/10/2020 08:11, Xiaoyun Li: > This example sets up a scenario that VXLAN packets can be received > by different PF queues based on VNID and each queue is bound to a VM > with a VNID so that the VM can receive its inner packets. > > Usually, OVS is used to do the software encap/decap for VXLAN pa

Re: [dpdk-dev] [PATCH v2] examples/tep_term: deprecate this example

2020-10-20 Thread Ferruh Yigit
On 10/20/2020 7:11 AM, Xiaoyun Li wrote: This example sets up a scenario that VXLAN packets can be received by different PF queues based on VNID and each queue is bound to a VM with a VNID so that the VM can receive its inner packets. Usually, OVS is used to do the software encap/decap for VXLAN

[dpdk-dev] [PATCH v2] examples/tep_term: deprecate this example

2020-10-19 Thread Xiaoyun Li
This example sets up a scenario that VXLAN packets can be received by different PF queues based on VNID and each queue is bound to a VM with a VNID so that the VM can receive its inner packets. Usually, OVS is used to do the software encap/decap for VXLAN packets. And the VXLAN packets offloading