From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f177.google.com (mail-wr0-f177.google.com [209.85.128.177]) by dpdk.org (Postfix) with ESMTP id 86DCA1075 for ; Tue, 14 Mar 2017 10:31:30 +0100 (CET) Received: by mail-wr0-f177.google.com with SMTP id u108so119685052wrb.3 for ; Tue, 14 Mar 2017 02:31:30 -0700 (PDT) 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=eGT++8KCmGMcAaGCUPS+ZRRQKlX8Ddqbwu/UBpBYk+E=; b=q7HsxostFBcFCiuZFy+6K8/t/F1B8/FH7mpGhN6/fR1TzdLbg0WzDK0hme3BQDbN7M XYT0AHh0mA87+5RK8njRLr3KNRcj5a5w3IXx2EVdJy7PoDmmgYdSooJJ5FIvaaF2k6+3 +hqJdUzJAuwTSAIsZ66gwtdT/d3MKgYYq3B4oWAxG1ZWSM6ObnEB5t3YKk4mafmv4IJq nnSXEHS3bpB+d1DbaOA8BPzlKQ69tDZk6sfyHvpqE6ybwFWcs1NNKYUyqskhlHXIGQOd lVT+DZaCQhWdBGnLam8aHCalLmRU6kBX5SfomD8LUo9QgK3YypCf/HE7lmQjXdhzWjaR mEJg== 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=eGT++8KCmGMcAaGCUPS+ZRRQKlX8Ddqbwu/UBpBYk+E=; b=F84c9YNqYniEg6YtPvW9Vsbg+/Dj/WhGBEdnw/QafqoBMUstNojzGaglwnCI1wbjsC pjFe1NfuoWXauCGHJbnoJ/j3CIiOt9KN0UeCfImQ+b0z6MaWU9xc5AuysfiTPrM0OhW6 WibL4Q2ADuZtReb75NExDK9XFy870JtRjCU9y7F370t3pIg1FlQTl3AK3wukdrxrLbBq acP0HTJQDrljId/A/2uqDK1YMux2j/kvLCyg/XuOFcFOwBKBO1k7YrlLXDQy7GBOGpo1 iuqGb6Eavxy2MKcC1KqgWvp5itbR80dm7DbSTopTsUQ+qTRRL1pqdi6caatcRSNDfYOH eNzw== X-Gm-Message-State: AMke39nn148sdAOaZTSWrw/vJHxJfL2XTF7L8mGKk9v76fxY9GVPozy+YgpugM8gKBX4YgOq X-Received: by 10.223.141.148 with SMTP id o20mr33404421wrb.75.1489483890216; Tue, 14 Mar 2017 02:31:30 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id 136sm14716344wms.32.2017.03.14.02.31.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Mar 2017 02:31:29 -0700 (PDT) From: Thomas Monjalon To: "Wu, Jingjing" Cc: "Zhang, Helin" , "Mcnamara, John" , dev@dpdk.org, ferruh.yigit@intel.com Date: Tue, 14 Mar 2017 10:31:28 +0100 Message-ID: <3110305.l4UWzxzWQC@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <17951395.s0M76qHr7t@xps13> References: <32336171.7h5g7kEJXa@xps13> <6154321.GLCpcWPPOA@xps13> <17951395.s0M76qHr7t@xps13> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 09:31:30 -0000 ping again 2017-03-08 12:25, Thomas Monjalon: > ping - still waiting for answers to below questions, please > > 2017-02-16 15:55, Thomas Monjalon: > > 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?