From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 1/3] ethdev: extend struct to support flow director in VFs Date: Sun, 01 Nov 2015 15:27:41 +0100 Message-ID: <7872129.vXpfkMljjd@xps13> References: <1446021688-17544-1-git-send-email-jingjing.wu@intel.com> <1446308653-2378-1-git-send-email-jingjing.wu@intel.com> <1446308653-2378-2-git-send-email-jingjing.wu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Jingjing Wu Return-path: Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id F136A256 for ; Sun, 1 Nov 2015 15:28:56 +0100 (CET) Received: by wmeg8 with SMTP id g8so41145526wme.0 for ; Sun, 01 Nov 2015 06:28:56 -0800 (PST) In-Reply-To: <1446308653-2378-2-git-send-email-jingjing.wu@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-11-01 00:24, Jingjing Wu: > This patch extends struct rte_eth_fdir_flow_ext to support flow > director in VFs. [...] > --- a/lib/librte_ether/rte_eth_ctrl.h > +++ b/lib/librte_ether/rte_eth_ctrl.h > @@ -426,6 +426,8 @@ struct rte_eth_fdir_flow_ext { > uint16_t vlan_tci; > uint8_t flexbytes[RTE_ETH_FDIR_MAX_FLEXLEN]; > /**< It is filled by the flexible payload to match. */ > + uint8_t is_vf; /**< 1 for VF, 0 for port dev */ > + uint16_t dst_id; /**< VF ID, available when is_vf is 1*/ > }; Why adding these parameters in an input struct? Shouldn't it be in rte_eth_fdir_action along with rx_queue?