From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 6544539EA for ; Thu, 16 Feb 2017 11:03:50 +0100 (CET) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga104.jf.intel.com with ESMTP; 16 Feb 2017 02:03:49 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,168,1484035200"; d="scan'208";a="65389547" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga005.jf.intel.com with ESMTP; 16 Feb 2017 02:03:49 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 16 Feb 2017 02:03:49 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.88]) by SHSMSX104.ccr.corp.intel.com ([10.239.4.70]) with mapi id 14.03.0248.002; Thu, 16 Feb 2017 18:03:47 +0800 From: "Xu, Qian Q" To: Thomas Monjalon , "Zhang, Helin" , "Wu, Jingjing" CC: "Mcnamara, John" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] i40e queues per VF Thread-Index: AQHShqpEnEsLaUDzu0amxjOX/RgonKFralvw Date: Thu, 16 Feb 2017 10:03:46 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B51BCCA@shsmsx102.ccr.corp.intel.com> References: <32336171.7h5g7kEJXa@xps13> In-Reply-To: <32336171.7h5g7kEJXa@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 queues per VF 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: Thu, 16 Feb 2017 10:03:51 -0000 Helin/Jingjing Could you give some answers here? Thx.=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Tuesday, February 14, 2017 6:07 PM > To: Zhang, Helin ; Wu, Jingjing > Cc: Mcnamara, John ; dev@dpdk.org > Subject: [dpdk-dev] i40e queues per VF >=20 > Hi, >=20 > When reading the documentation, it is not easy to understand the capabili= ty of > i40evf for the number of queues. >=20 > First, please could you explain why we need a build-time config option? > In the doc, there is neither justification nor tuning guidelines: >=20 > http://dpdk.org/doc/guides/nics/i40e.html#config-file-options > " > CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_PF (default 64) Number of > queues reserved for PF. > CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VF (default 4) Number of > queues reserved for each SR-IOV VF. > " >=20 > I feel these are hard limits and should be some constants in the code, no= t some > build configuration options. >=20 > The other doc to look at is: > http://dpdk.org/doc/guides/nics/intel_vf.html#intel-fortville-10-40-gigab= it- > ethernet-controller-vf-infrastructure > " > Each VF can have a maximum of 16 queue pairs. > " >=20 > Do we agree that a queue pair is 1 Rx queue / 1 Tx queue? > Note: the concept of queue pairs in Intel VF should be explained somewher= e. >=20 > Below, a different limitation is given: > " > The available queue number(at most 4) per VF depends on the total number = of > pool, which is determined by the max number of VF at PF initialization st= age and > the number of queue specified in config " >=20 > So what is the real maximum of queue pairs? 4 or 16? > The datasheet talks about 16 queues. Is it 8 pairs? >=20 > Is there something to configure the number of queues when creating VF wit= h the > kernel driver?