From patchwork Tue Feb 22 14:31:48 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Loftus, Ciara" X-Patchwork-Id: 107974 X-Patchwork-Delegate: ferruh.yigit@amd.com Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 176A6A0350; Tue, 22 Feb 2022 15:31:56 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DC9AC40DF6; Tue, 22 Feb 2022 15:31:55 +0100 (CET) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mails.dpdk.org (Postfix) with ESMTP id 91F1440DF4 for ; Tue, 22 Feb 2022 15:31:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645540313; x=1677076313; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=oAQ6q97KE8Vj28lXBQT8T9d8x4owEwPEL4rtuOzVfM0=; b=Re9hngpuQjJ/PvWIQjq1d7Ox3RGo+85cg9hHEmgpwjCXySfOw7lMJw/j LU4iLYEihoIGZf7p1F6mbUVSgm1JB4xmSjOU8J4jbJ0v1Hyk6KYGRbDHB shIKlmMhr7ZzQx0McIRANab85Ln04mQK5hG9y0JyvIT5HeX3sQYI8W4Mm UdgLx+JzYFdrOPVm0UWVc18sSCZo66ew7s3gBC6lVCYNPwTHAURNiFtqB r+cLeL8NluzFiHXeCe9iHtyeDYxlEX+wVyzgbNs7/zJee388tZE2poMfE 7EywO/1DcMun+hsVwfZovNYmAFBBu0KrMJZNO/yrsOOhXyURK+qXTXmqu w==; X-IronPort-AV: E=McAfee;i="6200,9189,10265"; a="249295541" X-IronPort-AV: E=Sophos;i="5.88,387,1635231600"; d="scan'208";a="249295541" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Feb 2022 06:31:52 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.88,387,1635231600"; d="scan'208";a="776321363" Received: from silpixa00399839.ir.intel.com (HELO localhost.localdomain) ([10.237.222.159]) by fmsmga006.fm.intel.com with ESMTP; 22 Feb 2022 06:31:51 -0800 From: Ciara Loftus To: dev@dpdk.org Cc: ferruh.yigit@intel.com, Ciara Loftus Subject: [PATCH] net/af_xdp: update doc with information on queue setup Date: Tue, 22 Feb 2022 14:31:48 +0000 Message-Id: <20220222143148.14502-1-ciara.loftus@intel.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 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 When an AF_XDP PMD is created without specifying the 'start_queue', the default Rx queue associated with the socket will be Rx queue 0. A common scenario encountered by users new to AF_XDP is that they create the socket on queue 0 however their interface is configured with many more queues. In this case, traffic might land on for example queue 18 which means it will never reach the socket. This commit updates the AF_XDP documentation with instructions on how to configure the interface to ensure the traffic will land on queue 0 and thus reach the socket successfully. Signed-off-by: Ciara Loftus Acked-by: Ferruh Yigit --- doc/guides/nics/af_xdp.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/guides/nics/af_xdp.rst b/doc/guides/nics/af_xdp.rst index ee1e146a9e..ba3ee6a2f0 100644 --- a/doc/guides/nics/af_xdp.rst +++ b/doc/guides/nics/af_xdp.rst @@ -64,6 +64,16 @@ The following example will set up an af_xdp interface in DPDK: --vdev net_af_xdp,iface=ens786f1 +If 'start_queue' is not specified in the vdev arguments, the socket will by +default be created on Rx queue 0. To ensure traffic lands on this queue, one can +use flow steering if the network card supports it. Or, a simpler way is to +reduce the number of configured queues for the device which will ensure that all +traffic will land on queue 0 and thus reach the socket: + +.. code-block:: console + + ethtool -L ens786f1 combined 1 + Limitations -----------