From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id CBA542C1A for ; Tue, 5 Apr 2016 10:49:28 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga104.fm.intel.com with ESMTP; 05 Apr 2016 01:49:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,443,1455004800"; d="scan'208";a="681008921" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by FMSMGA003.fm.intel.com with ESMTP; 05 Apr 2016 01:49:29 -0700 Received: from fmsmsx155.amr.corp.intel.com (10.18.116.71) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 5 Apr 2016 01:49:27 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX155.amr.corp.intel.com (10.18.116.71) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 5 Apr 2016 01:49:27 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.232]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.18]) with mapi id 14.03.0248.002; Tue, 5 Apr 2016 16:49:25 +0800 From: "Chen, Jing D" To: Thomas Monjalon CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v2] doc: update nic overview Thread-Index: AQHRi/RndhRsqiD+70KQcGSYuBoeLZ91IB4AgAX20XA= Date: Tue, 5 Apr 2016 08:49:24 +0000 Message-ID: <4341B239C0EFF9468EE453F9E9F4604D0446DA34@shsmsx102.ccr.corp.intel.com> References: <1459499949-9657-1-git-send-email-jing.d.chen@intel.com> <1459500924-10259-1-git-send-email-jing.d.chen@intel.com> <7642275.Irj43jkQ8Y@xps13> In-Reply-To: <7642275.Irj43jkQ8Y@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 v2] doc: update nic overview 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: Tue, 05 Apr 2016 08:49:29 -0000 Thomas, > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Saturday, April 02, 2016 5:40 AM > To: Chen, Jing D > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v2] doc: update nic overview >=20 > 2016-04-01 16:55, Chen Jing D: > > Add feature support list for fm10k, fm10k-vec, fm10kvf and > > fm10kvf-vec. >=20 > Please help me to understand what is fm10kvf. > I see only one fm10k driver: > % git grep 'struct eth_driver' drivers/net/fm10k/ > drivers/net/fm10k/fm10k_ethdev.c:static struct eth_driver rte_pmd_fm10k > =3D { You can refer to below definition: static const struct rte_pci_id pci_id_fm10k_map[] =3D { #define RTE_PCI_DEV_ID_DECL_FM10K(vend, dev) { RTE_PCI_DEVICE(vend, dev) }, #define RTE_PCI_DEV_ID_DECL_FM10KVF(vend, dev) { RTE_PCI_DEVICE(vend, dev) = }, #include "rte_pci_dev_ids.h" { .vendor_id =3D 0, /* sentinel */ }, }; As you can see that fm10k driver will manage 2 different types of devices, = PF and VF.=20 We can say that there are 2 drivers under fm10k directory. The aspects that= not applicable to PF/VF will use condition check to control execution path. This makes dri= ver can work with PF and VF devices and reduce redundant code.=20