From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 95439108F for ; Tue, 17 Jan 2017 01:35:47 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga105.fm.intel.com with ESMTP; 16 Jan 2017 16:35:46 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,241,1477983600"; d="scan'208";a="214094889" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga004.fm.intel.com with ESMTP; 16 Jan 2017 16:35:46 -0800 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 16 Jan 2017 16:35:46 -0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 16 Jan 2017 16:35:46 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by SHSMSX103.ccr.corp.intel.com ([10.239.4.69]) with mapi id 14.03.0248.002; Tue, 17 Jan 2017 08:35:44 +0800 From: "Lu, Wenzhuo" To: Thomas Monjalon CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v10 26/26] doc: update doc for VFD Thread-Index: AQHSb7zMoaDmQXSMtEOWGY6F0t6ZM6E6Wm0AgAF5JhA= Date: Tue, 17 Jan 2017 00:35:42 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B55A475@shsmsx102.ccr.corp.intel.com> References: <1480637533-37425-1-git-send-email-wenzhuo.lu@intel.com> <1484545911-40432-1-git-send-email-wenzhuo.lu@intel.com> <1484545911-40432-27-git-send-email-wenzhuo.lu@intel.com> <1553461.x6iY0G4dk3@xps13> In-Reply-To: <1553461.x6iY0G4dk3@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] [PATCH v10 26/26] doc: update doc for VFD 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, 17 Jan 2017 00:35:48 -0000 Hi Thomas, > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Monday, January 16, 2017 6:05 PM > To: Lu, Wenzhuo > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v10 26/26] doc: update doc for VFD >=20 > 2017-01-16 13:51, Wenzhuo Lu: > > --- a/doc/guides/rel_notes/release_17_02.rst > > +++ b/doc/guides/rel_notes/release_17_02.rst > > @@ -66,6 +66,35 @@ New Features > > Support for Mellanox ConnectX-5 family of 10/25/40/50/100 Gbps adapt= ers > > has been added to the existing mlx5 PMD. > > > > +* **Added VF Daemon (VFD) on i40e. - EXPERIMENTAL** > > + > > + This's an EXPERIMENTAL feature to enhance the capability of DPDK PF > > + as many VF management features are not supported by kernel PF driver= . > > + Some new private APIs are implemented in PMD without abstrction laye= r. >=20 > Typo in abstrction >=20 > > + They can be used directly by some users who have the need. > > + > > + The new APIs to control VFs directly from PF include, > > + 1) set VF MAC anti-spoofing > > + 2) set VF VLAN anti-spoofing > > + 3) set TX loopback > > + 4) set VF unicast promiscuous mode > > + 5) set VF multicast promiscuous mode > > + 6) set VF MTU > > + 7) get/reset VF stats > > + 8) set VF MAC address > > + 9) set VF VLAN stripping > > + 10) VF VLAN insertion > > + 12) set VF broadcast mode > > + 13) set VF VLAN tag > > + 14) set VF VLAN filter > > + VFD also includes VF to PF mailbox message management by APP. > > + When PF receives mailbox messages from VF, PF should call the > > + callback provided by APP to know if they're permitted to be processe= d. > > + > > + As an EXPERIMENTAL feature, please aware it can be changed or even > > + removed without prior notice. >=20 > It is good to explain things in the release notes, but not sufficient. > We must explain the DPDK position about PF/VF in the design doc: > http://dpdk.org/doc/guides/contributing/design.html >=20 > It is important to explain that the primary goal of DPDK is to provide a > userland dataplane. Managing VF from a PF driver is a control plane featu= re > and we generally rely on the kernel for that. > So we continue adding some PF features in DPDK as experimental functions > but they must be implemented in the kernel with the same messaging > interface. Sure. Will update the doc with a v11.