From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id CE1892C74 for ; Tue, 14 Mar 2017 14:59:56 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1489499996; x=1521035996; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=5Bjp8p7gHhQsFkzBLYZnzH99KL7y8EUeTGI/FW0zfGY=; b=Vhj9zwBUtkc4lNOx015478C7hOWZ7V8N5TeXpAH+A2Wj7SOrd8a5B1Qc 5HPCEfB4urVqBwmRD3GJNxxBiJOsGg==; Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Mar 2017 06:59:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,164,1486454400"; d="scan'208";a="75261415" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga005.jf.intel.com with ESMTP; 14 Mar 2017 06:59:55 -0700 Received: from fmsmsx112.amr.corp.intel.com (10.18.116.6) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 14 Mar 2017 06:59:55 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX112.amr.corp.intel.com (10.18.116.6) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 14 Mar 2017 06:59:55 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.177]) with mapi id 14.03.0248.002; Tue, 14 Mar 2017 21:59:53 +0800 From: "Chen, Jing D" To: Thomas Monjalon , "Zhang, Helin" , "Wu, Jingjing" CC: "Yigit, Ferruh" , "vincent.jardin@6wind.com" , "dev@dpdk.org" Thread-Topic: i40e SR-IOV with Linux PF Thread-Index: AQHSnAY5lX5E3hDz70yVuUvgALEbB6GST/aAgAIN+cA= Date: Tue, 14 Mar 2017 13:59:52 +0000 Message-ID: <4341B239C0EFF9468EE453F9E9F4604D3C6036BB@shsmsx102.ccr.corp.intel.com> References: <248236628.l6b5mhHNAu@xps13> <1623193.ZGhhn5RSHY@xps13> In-Reply-To: <1623193.ZGhhn5RSHY@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 Subject: Re: [dpdk-dev] i40e SR-IOV with Linux PF X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 13:59:57 -0000 >=20 > +Cc dev@dpdk.org >=20 > 2017-03-13 15:29, Thomas Monjalon: > > Hi i40e developers, > > > > Referring to the VFD discussion, I thought basic behaviours were the > > same regardless of the PF driver: > > http://dpdk.org/ml/archives/dev/2016-December/053056.html > > " > > > In the meanwhile, we have some test models ongoing to validate > > > combination of Linux and DPDK drivers for VF and PF. > > > We'll fully support below 4 cases going forward. > > > 1. DPDK PF + DPDK VF > > > 2. DPDK PF + Linux VF > > > 3. Linux PF + DPDK VF > > > 4. Linux PF + Linux VF (it's not our scope) > > [...] > > > Linux PF + DPDK VF has been tested with 1.0 API long time ago. > > > There is some test activities ongoing. > > " > > > > I think the Linux PF case is important and deserves more consideration. > > When looking at the code, specifically i40evf_vlan_offload_set() and > > i40evf_vlan_pvid_set(), I read this: > > " > > /* Linux pf host doesn't support vlan offload yet */ > > if (vf->version_major =3D=3D I40E_DPDK_VERSION_MAJOR) { " > > > > Is there some work in progress on Linux side to get the same behaviour > > as with a DPDK PF? > > > > At least, it must be documented in > > doc/guides/nics/features/i40e_vf.ini > > and marked as partially supported (P instead of Y) in > > doc/guides/nics/i40e.rst Thanks for pointing it out. We'll sync our code with latest kernel driver a= nd document and comment properly soon.