From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by dpdk.org (Postfix) with ESMTP id 74A7C8E6F for ; Fri, 25 Sep 2015 09:01:45 +0200 (CEST) Received: by wicfx3 with SMTP id fx3so9009325wic.1 for ; Fri, 25 Sep 2015 00:01:45 -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=Qgg9g6ne0pEXqGy5i87XmHF3C5W7N+glOKKFnDIFU+s=; b=GsGcbrizX5DMnFS8VT3qAAa9e/XJlPVTKeoLmjzf33YhWO7XaJo1gM/IAHRlQnzXgn TVoFqJC0+J6ACXinsvXtUtx7idyujEpQkE3DutiRUDzGc8tcExnyF2D3woFDMeh7KMe2 Cf8w7TGfTIuyBGmAh4NCMJZ7yrrZ7xkZ6HEB0KmMN8IMpal9bW/B198nvb4x0BNXGN2S ov7yaVgIxrVEdeKX8/z92ZqKha8V19QeTClpHtouodv2ed+YgHnPnqJxbsmPzdJIKLFd UFkgMqQ347TaKrflHawdkrXkvSphnGaFRczRZ5kC6Z/Sh2ltM82l9VO7MH/2aauLZjmx D+QA== X-Gm-Message-State: ALoCoQmWXMrdBiIgK20EjANqm/h7YBp81G0bTRi69Kvz3smTLe+ByXh4IPDUlplQmvJX9XKLvWfi X-Received: by 10.194.116.67 with SMTP id ju3mr3997723wjb.143.1443164505187; Fri, 25 Sep 2015 00:01:45 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id jc9sm1739676wic.6.2015.09.25.00.01.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Sep 2015 00:01:44 -0700 (PDT) From: Thomas Monjalon To: Wenzhuo Lu Date: Fri, 25 Sep 2015 09:00:39 +0200 Message-ID: <2216065.qpkPQE5WLk@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1443161125-1035-2-git-send-email-wenzhuo.lu@intel.com> References: <1443161125-1035-1-git-send-email-wenzhuo.lu@intel.com> <1443161125-1035-2-git-send-email-wenzhuo.lu@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 1/6] lib/librte_ether: modify the structures for fdir new modes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 07:01:45 -0000 2015-09-25 14:05, Wenzhuo Lu: > +enum rte_fdir_mode { > + RTE_FDIR_MODE_NONE = 0, /**< Disable FDIR support. */ > + RTE_FDIR_MODE_SIGNATURE, /**< Enable FDIR signature filter mode. */ > + RTE_FDIR_MODE_PERFECT, /**< Enable FDIR perfect filter mode for IP. */ > + RTE_FDIR_MODE_PERFECT_MAC_VLAN, /**< Enable FDIR filter mode - MAC VLAN. */ > + RTE_FDIR_MODE_PERFECT_CLOUD, /**< Enable FDIR filter mode - cloud. */ > +}; I know that some Intel NICs use the terminology "cloud" in their datasheet, but it is meaningless. [...] > +/** > + * A structure used to define the input for VxLAN NVGRE flow > + */ > +struct rte_eth_cloud_flow { > + enum rte_eth_fdir_tunnel_type tunnel_type; /**< Tunnel type to match. */ > + uint32_t tni_vni; /**< TNI or VNI to match. */ Isn't it Intel-specific? > + struct ether_addr mac_addr; /**< Mac address to match. */ > +}; So it is a tunnel, currently only VXLAN or NVGRE. And this kind of tunnel can be used in a cloud datacenter, yes. Or elsewhere. Please use the "tunnel" word.