From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas.monjalon@6wind.com> Received: from mail-wr0-f179.google.com (mail-wr0-f179.google.com [209.85.128.179]) by dpdk.org (Postfix) with ESMTP id 505AC47CD for <dev@dpdk.org>; Thu, 16 Feb 2017 15:55:37 +0100 (CET) Received: by mail-wr0-f179.google.com with SMTP id 89so8833641wrr.3 for <dev@dpdk.org>; Thu, 16 Feb 2017 06:55:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=2U2acZZZrdf2ShR3UFt5mJ+/qVqrTJYfztj7PiRUijE=; b=TPUoVCuiAVHiAoXjfEywSDYD3v146/amL4HLolyjZcI9WrT0LQEafxvgEx7H47TmGY 9tLZ187FE7FfuTq/8yWVXEfOSdtPEoxXsv1oVtkbFW/k6Fkau6iLd+LDF7rZX4SGf/vN GS7A6vi1vCLYwQfJUbFABAhzusYpg8TjWyHPvzVW2GHt3F/IlbIWQoyeicCHqPS/b8Nf TDSQ+78rT2uZmtuND7d3TpyVedlYZ7kHO0ZTY4r2yOVdfLepH6dyVAa1yHa5QM4obskO F2KtTlNfp4UHOroIVcxlt1GXTp1TCAmkLo8QsnJMa7sga1PqKdoZnAkf8pd2G1TyL7TM HBJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=2U2acZZZrdf2ShR3UFt5mJ+/qVqrTJYfztj7PiRUijE=; b=oKOB1eNHiFGUhMZoXRP7d7p7fGPP9YJWuPbzd2ttih+TweulphE1FIDddrEycc2vdr xMojclY0ZUsrzcgCfd0dKeslqaSd+DUVoepzVvqOzJByOZ4a9N9tqz/A2yB/b6UzpIWS cDqJrR1RzCTG2ZIC4ESTKFvAr27PPKqZNiwYRFMp5K6ZZsl6hpix9iniE3D4NL+yCRMA 2Mv7FR0Pa38cQNqaF4zFcnUOTrov7JCntoJsQcciyHT9jjVNMXnDMGrFc3lzlgE+cAgN 1vak7JGOp6JPrcjS4+uqhLf6o+2GJMPNpFhUoubtfLYva5+FsiAhOzJMlBgJLQF9LXkf tFmg== X-Gm-Message-State: AMke39kdLBMEvO/Fdpa3YVSp7F3KNY0jvcKfUIkrLXw6v3pMy8Ev+MtkrfksgcZ7lUVejRxL X-Received: by 10.223.128.202 with SMTP id 68mr2941489wrl.92.1487256937087; Thu, 16 Feb 2017 06:55:37 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id y30sm9208413wrc.23.2017.02.16.06.55.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 06:55:36 -0800 (PST) From: Thomas Monjalon <thomas.monjalon@6wind.com> To: "Wu, Jingjing" <jingjing.wu@intel.com> Cc: "Zhang, Helin" <helin.zhang@intel.com>, "Mcnamara, John" <john.mcnamara@intel.com>, dev@dpdk.org Date: Thu, 16 Feb 2017 15:55:35 +0100 Message-ID: <6154321.GLCpcWPPOA@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <9BB6961774997848B5B42BEC655768F810CDE4AF@SHSMSX103.ccr.corp.intel.com> References: <32336171.7h5g7kEJXa@xps13> <9BB6961774997848B5B42BEC655768F810CDE4AF@SHSMSX103.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 16 Feb 2017 14:55:37 -0000 2017-02-16 13:58, Wu, Jingjing: > From: Thomas Monjalon > > > > Hi, > > > > When reading the documentation, it is not easy to understand the capability of > > i40evf for the number of queues. > > > > First, please could you explain why we need a build-time config option? > > In the doc, there is neither justification nor tuning guidelines: > > > > 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. > > " > > This number is used as initialization time to allocate queue number > for PF/VF for HW's queue pool. Will add more description in i40e.rst. The description "Number of queues reserved for each SR-IOV VF" seems partially wrong. Please explain it is a queue pair. > > I feel these are hard limits and should be some constants in the code, not some > > build configuration options. > > > > The other doc to look at is: > > http://dpdk.org/doc/guides/nics/intel_vf.html#intel-fortville-10-40-gigabit- > > ethernet-controller-vf-infrastructure > > " > > Each VF can have a maximum of 16 queue pairs. > > " > > > > 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 somewhere. > > > Yes. > > 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 stage and > > the number of queue specified in config " > > > I think there may be some inconsistent description in doc intel_vf.rst due to > Multiple kinds of NICs. We should correct them. > Thanks for pointing that. > > > So what is the real maximum of queue pairs? 4 or 16? > > The datasheet talks about 16 queues. Is it 8 pairs? > > That's is 16 queue pairs. 16 RX queues and 16 Tx queues. > > > > Is there something to configure the number of queues when creating VF with the > > kernel driver? > > In kernel driver, it seems at most only 4 queues are supported. That's > Why we add build-time config option to make more queues are possible. If we can create 16 queue pairs, why restrict the default configuration to 4? Why is it a build-time config option?