From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id D36DE5A6C for ; Mon, 2 Nov 2015 06:24:40 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP; 01 Nov 2015 21:24:39 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,233,1444719600"; d="scan'208";a="592300719" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by FMSMGA003.fm.intel.com with ESMTP; 01 Nov 2015 21:24:39 -0800 Received: from fmsmsx119.amr.corp.intel.com (10.18.124.207) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sun, 1 Nov 2015 21:24:39 -0800 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by FMSMSX119.amr.corp.intel.com (10.18.124.207) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sun, 1 Nov 2015 21:24:39 -0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.194]) by shsmsx102.ccr.corp.intel.com ([169.254.2.253]) with mapi id 14.03.0248.002; Mon, 2 Nov 2015 13:24:37 +0800 From: "Wu, Jingjing" To: Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH v3 1/3] ethdev: extend struct to support flow director in VFs Thread-Index: AQHRE/ifbLV/kqxF+0aHZ3nyhfij3p6GtOCAgACGslD//4EiAIAAiE3A Date: Mon, 2 Nov 2015 05:24:37 +0000 Message-ID: <9BB6961774997848B5B42BEC655768F8D0F8A2@SHSMSX104.ccr.corp.intel.com> References: <1446021688-17544-1-git-send-email-jingjing.wu@intel.com> <7872129.vXpfkMljjd@xps13> <9BB6961774997848B5B42BEC655768F8D0F1EC@SHSMSX104.ccr.corp.intel.com> <3422621.OhOAmi5lFO@xps13> In-Reply-To: <3422621.OhOAmi5lFO@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v3 1/3] ethdev: extend struct to support flow director in VFs 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: Mon, 02 Nov 2015 05:24:41 -0000 >=20 > Oh! > From the VM, using > rte_eth_dev_filter_ctrl(port_id, filter_type, filter_op, arg) > it can be deduced from the VF device, no? > Is the use case to define a VF flow director outside of the VM? Yes, if VM can configure through rte_eth_dev_filter_ctrl, it will be better= . But flow director can only be programed on PF, and currently there is no su= ch virtual channel between PF and VF in share code. Due to the principle align= ed with i40e kernel driver develop, we cannot add new virtual channel by ourse= lves. So I did it this way on DPDK when DPDK using as PF driver. Thanks Jingjing