Re: [PATCH 3/6]i40e:Add VxLAN Cloud filter API

Hi Thomas,

-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org]
Sent: Tuesday, August 12, 2014 6:40 PM
To: Liu, Jijiang
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [dpdk-dev] [PATCH 3/6]i40e:Add VxLAN Cloud filter API

Hi Jijiang,

2014-08-12 11:12, Jijiang Liu:

quoted

Support VxLAN cloud filters,which is used to use MAC, VLAN to point
   to a queue. The filter types supported include below:
   1. Inner MAC and Inner VLAN ID
   2. Inner MAC address and inner VLAN ID, tenned ID.
   3. Inner MAC and tenant ID
   4. Inner MAC address
   5. Outer MAC address, tenant ID and inner MAC

Signed-off-by: jijiangl <redacted>
Acked-by: Helin Zhang <redacted>
Acked-by: Jingjing Wu <redacted>
Acked-by: Jing Chen <redacted>
---
 lib/librte_ether/rte_ethdev.c     |   50 ++++++++++++++++
 lib/librte_ether/rte_ethdev.h     |   72 ++++++++++++++++++++++++
 lib/librte_pmd_i40e/i40e_ethdev.c |  112
+++++++++++++++++++++++++++++++++++++
 3 files changed, 234 insertions(+), 0 deletions(-)

I prefer to have a separated commit for API (ethdev) and another one for
implementation (i40e).

About API, why name it cloud filter instead of VxLAN?

Ok, I can separate the commit into two patches.

VxLAN is just a kind tunnel type, there are another tunnel types based on protocol type, they are below.
Tunnel Type:
* 0x0: VXLAN
* 0x1: NVGRE or other MAC in GRE
* 0x2: Geneve
  0x3: IP in GRE
Currently, I just implemented VxLAN tunnel type, and we will support another tunnel types in cloud filter API later.