From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5FE93A00C5; Wed, 16 Feb 2022 17:06:49 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4DA5D410FF; Wed, 16 Feb 2022 17:06:49 +0100 (CET) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by mails.dpdk.org (Postfix) with ESMTP id 6B8D240150; Wed, 16 Feb 2022 17:06:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645027607; x=1676563607; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=aBzsuVz+Ia2E0V8xdESboLKQem4VrwwOF+35mO99IwU=; b=FzGAJwkK+joFYu9fBVO7PUvgLCHi3/8OGrMhoy7lKyhR2SafFLa+5ljG GLwQzFLuj9DAo2LGLNeIKhiHV01lnV2d52/RWQ25Aq2c8r61fzkYQEdWg FKpkiJKJ/SXQIRYadMxR1r0kwEa+gyMRRYFyQ9jSsaumCi84jl3c9u9qd 4c/qA2SrL8bqNGVjR5j8s4sqFrPTHA24LSXZGGjiRbwly85Cpl6Rrhb1G tQbVndV7W58J7iAEiO0heSteLfcLEsRmuGlrI6gEbWu2lavdKjFKwdLRF 4t37WICQ68aa105F0cCMxsMZ8FnSrH8BJn44/1IzYnM3MExnF3HZ/lQCZ Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10260"; a="231279735" X-IronPort-AV: E=Sophos;i="5.88,374,1635231600"; d="scan'208";a="231279735" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Feb 2022 08:06:46 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.88,374,1635231600"; d="scan'208";a="704363290" Received: from silpixa00401026.ir.intel.com ([10.243.22.62]) by orsmga005.jf.intel.com with ESMTP; 16 Feb 2022 08:06:44 -0800 From: Bruce Richardson To: dev@dpdk.org Cc: Bruce Richardson , stable@dpdk.org, Kevin Laatz Subject: [PATCH 3/3] doc/dmadev/idxd: improve configuration examples Date: Wed, 16 Feb 2022 16:06:09 +0000 Message-Id: <20220216160610.475242-4-bruce.richardson@intel.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220216160610.475242-1-bruce.richardson@intel.com> References: <20220216160610.475242-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org The documentation on how to configure device instances using accel-config can be improved by a number of changes: * For initial example, when only configuring one queue, omit configuration of a second engine, which is unused later. * Add the "max-batch-size" setting to the options being configured for each queue * Add a final, more complete example, showing configuration of multiple queues on a device. Cc: stable@dpdk.org Signed-off-by: Bruce Richardson --- Note: although not strictly a bug fix, this doc update is a good candidate for backport to 21.11, so cc'ing stable --- doc/guides/dmadevs/idxd.rst | 29 +++++++++++++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/doc/guides/dmadevs/idxd.rst b/doc/guides/dmadevs/idxd.rst index 8d7cea6583..bdfd3e78ad 100644 --- a/doc/guides/dmadevs/idxd.rst +++ b/doc/guides/dmadevs/idxd.rst @@ -55,7 +55,6 @@ such as priority or queue depth, need to be set for each queue. To assign an engine to a group:: $ accel-config config-engine dsa0/engine0.0 --group-id=0 - $ accel-config config-engine dsa0/engine0.1 --group-id=1 To assign work queues to groups for passing descriptors to the engines a similar accel-config command can be used. However, the work queues also need to be configured depending on the use case. @@ -71,7 +70,7 @@ Example configuration for a work queue:: $ accel-config config-wq dsa0/wq0.0 --group-id=0 \ --mode=dedicated --priority=10 --wq-size=8 \ - --type=user --name=dpdk_app1 + --max-batch-size=512 --type=user --name=dpdk_app1 Once the devices have been configured, they need to be enabled:: @@ -82,6 +81,32 @@ Check the device configuration:: $ accel-config list +Every Intel\ |reg| DSA instance supports multiple queues and each should be similarly configured. +As a further example, the following set of commands will configure and enable 4 queues on instance 0, +giving each an equal share of resources:: + + # configure 4 groups, each with one engine + accel-config config-engine dsa0/engine0.0 --group-id=0 + accel-config config-engine dsa0/engine0.1 --group-id=1 + accel-config config-engine dsa0/engine0.2 --group-id=2 + accel-config config-engine dsa0/engine0.3 --group-id=3 + + # configure 4 queues, putting each in a different group, so each + # is backed by a single engine + accel-config config-wq dsa0/wq0.0 --group-id=0 --type=user --wq-size=32 \ + --priority=10 --max-batch-size=1024 --mode=dedicated --name=dpdk_app1 + accel-config config-wq dsa0/wq0.1 --group-id=1 --type=user --wq-size=32 \ + --priority=10 --max-batch-size=1024 --mode=dedicated --name=dpdk_app1 + accel-config config-wq dsa0/wq0.2 --group-id=2 --type=user --wq-size=32 \ + --priority=10 --max-batch-size=1024 --mode=dedicated --name=dpdk_app1 + accel-config config-wq dsa0/wq0.3 --group-id=3 --type=user --wq-size=32 \ + --priority=10 --max-batch-size=1024 --mode=dedicated --name=dpdk_app1 + + # enable device and queues + accel-config enable-device dsa0 + accel-config enable-wq dsa0/wq0.0 dsa0/wq0.1 dsa0/wq0.2 dsa0/wq0.3 + + Devices using VFIO/UIO drivers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.32.0