From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-we0-f170.google.com (mail-we0-f170.google.com
 [74.125.82.170]) by dpdk.org (Postfix) with ESMTP id 0FB5C678D
 for <dev@dpdk.org>; Wed, 13 Aug 2014 15:48:09 +0200 (CEST)
Received: by mail-we0-f170.google.com with SMTP id w62so11326237wes.1
 for <dev@dpdk.org>; Wed, 13 Aug 2014 06:51:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=hm5PPRLTYquM2jNoGx4jTTyebpeMHgco9DuaBAZ5DQM=;
 b=PnmHztd83uil/z4NbLb/uZXOhrVvOn14uN5TrYMyvchHkTuPaD3LFKw+CQqbo/eWoa
 dMlRgIftQ0E1TbYzJcFm0PhbuEkeD55++b+S3ZwOIYGOTMjsXCsWx+TAesjGRvshnED2
 76x7+oFU6HzkL4ixZUDDexo7hNUoNZVK50GVVA9fItC0AXKQPsCD8yxU3M/U1dvoNVtk
 sCKmrIRKPc7efraJYdC26og+SfbtW+vYPu82bO57pNzipAahnRRTvn+B2zN8sHF6U0lG
 FlD863CBD8y0EaNbkg2aBjt9tQ9Z1SOhwI+LWex2UiRXeDiDjVsbmAT/SeuEEJEG8DRA
 I35Q==
X-Gm-Message-State: ALoCoQlOrQx1roikJHkAiqdiRGX+WLsu0tCNAmVR8rPWnk59xnN18DEBxPTFecsxBlGutfST3kKn
X-Received: by 10.180.99.34 with SMTP id en2mr35529235wib.34.1407937869190;
 Wed, 13 Aug 2014 06:51:09 -0700 (PDT)
Received: from xps13.localnet (APoitiers-651-1-287-159.w86-206.abo.wanadoo.fr.
 [86.206.174.159])
 by mx.google.com with ESMTPSA id ft6sm13355282wic.0.2014.08.13.06.51.07
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 13 Aug 2014 06:51:08 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Liu, Jijiang" <jijiang.liu@intel.com>
Date: Wed, 13 Aug 2014 15:50:50 +0200
Message-ID: <4346025.4OV9mqUq5g@xps13>
Organization: 6WIND
User-Agent: KMail/4.13.3 (Linux/3.15.8-1-ARCH; KDE/4.13.3; x86_64; ; )
In-Reply-To: <1ED644BD7E0A5F4091CF203DAFB8E4CC01D5FCDE@SHSMSX101.ccr.corp.intel.com>
References: <1407813127-10991-1-git-send-email-jijiang.liu@intel.com>
 <1875158.2CzkkyWnXV@xps13>
 <1ED644BD7E0A5F4091CF203DAFB8E4CC01D5FCDE@SHSMSX101.ccr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/6]i40e:Add VxLAN Cloud filter API
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Aug 2014 13:48:09 -0000

2014-08-13 08:23, Liu, Jijiang:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > About API, why name it cloud filter instead of VxLAN?
> 
> 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.

OK, I understand. But cloud filter is just a marketing name.
Please let's stick to technical and precise names.
It seems these tunnels are L2 over IP, right?

-- 
Thomas