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 9666FA09E4 for ; Fri, 29 Jan 2021 17:50:26 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7EEB04069F; Fri, 29 Jan 2021 17:50:26 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 5C2A44067B for ; Fri, 29 Jan 2021 17:50:23 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 8B6035C01DE; Fri, 29 Jan 2021 11:50:22 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 29 Jan 2021 11:50:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm3; bh= TiD7jS7MEZxGTzTPcIJcV5H8mZEYBNIRkoXUB2DxZ7k=; b=pKwcs3aaeGjDMi38 7ebe064K/orqeP8MzMofASOyPom2yWWceJSYLGlN19Mp7BgeaYeltAgETY4M8t7D cgiJqpUN7w6NId9dYH1JbL4YPQezNE+izhHSTB1cwzg8mir2ejrGPCssVDqCoJAz GtLh8Blws7yjuHXUnsrlghiNxPw0tPOvE162eDAX2g9rV4Egv859WzuLJQMPbtrN apKaiYqeOy8A7VuIYAfaPTBdEMnRf23Kadq3i+H0j4bij6EhFsaW0aOtseDgpqMP BWWozxubyoAKkqkO7uP7QzB2mHoTRIf7YIPyHNeN3ZOQEGuwvF8jowGl35L4lHo1 jKnDBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=TiD7jS7MEZxGTzTPcIJcV5H8mZEYBNIRkoXUB2DxZ 7k=; b=dpda07n6o8wXst9xDKbuiYvUs2kYbFfyPlThUVkH9p60sQXbsyvHQX8/7 B+kS3Xxknqm8DpVHJfWM/wRirzgXf77gp/MjtGoo1J+ktxsbiucoC4LJmmm4arJV BUQcuNUsgx31Hb3RirvhXbxEg5nriKz2DvRAEP36AT6ZdisA23YuAQagPiXy2fGX twkFX2amxrGdNIeZWjOs9hk1YE2BkTZe+OrMqoqtDFYT0iPMBDHakWqPJxsZSWFh p/hQ1Wc8iopSucFTGIKsV60ZSMrPes8wwK3j4VXQ3t1yHHOQ/epdpl5njYnidiYx czWiSclC1sHRcW3K+80ZTlsGkuO/Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgdelgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeffvdffjeeuteelfeeileduudeugfetjeelveefkeejfeeigeehteff vdekfeegudenucffohhmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvd dtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B00EA108005F; Fri, 29 Jan 2021 11:50:21 -0500 (EST) From: Thomas Monjalon To: Carsten Andrich Cc: users@dpdk.org, viacheslavo@nvidia.com Date: Fri, 29 Jan 2021 17:50:20 +0100 Message-ID: <1768623.GMc5ikO6cA@thomas> In-Reply-To: <43ddc3a8-a48f-0930-a2da-9e2fcdde1b98@tu-ilmenau.de> References: <43ddc3a8-a48f-0930-a2da-9e2fcdde1b98@tu-ilmenau.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-users] MLX5: Using packet send scheduling / packet pacing X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" +Cc Slava 29/01/2021 17:30, Carsten Andrich: > Hello everyone, > > I'm trying to use packet send scheduling [1] with DPDK 20.11 and the > MLX5 PMD (NIC: ConnectX-5 MCX516A-CDAT). This patch contains some > additional information on this feature also know as packet pacing [2]. > > According to MLX5's docs, packet pacing requires the "tx_pp" parameter > [3, CTRL+F: "tx_pp"]. However, when firing up testpmd with that > parameter, it fails as follows: > > > # dpdk-testpmd -a 81:00.0,tx_pp=500 -- -i > > ... > > EAL: Probe PCI driver: mlx5_pci (15b3:1019) device: 0000:81:00.0 (socket 0) > > mlx5_pci: WQE rate mode is required for packet pacing > > mlx5_pci: probe of PCI device 0000:81:00.0 aborted after encountering an error: No such device > > common_mlx5: Failed to load driver = mlx5_pci. > > > > EAL: Requested device 0000:81:00.0 cannot be used > The error message originates here [4] and is caused by what to me > appears to be a value read from the NIC [5]. Unfortunately, that leaves > me clueless on how to activate the required "WQE rate mode". According > to the output of ibv_devinfo, my NIC does support packet pacing: > > > # ibv_devinfo -v 81:00.0 > > ... > > packet_pacing_caps: > > qp_rate_limit_min: 1kbps > > qp_rate_limit_max: 100000000kbps > > supported_qp: > > SUPPORT_RAW_PACKET > I'd be grateful for any information on how to get packet pacing up and > running. Am I just missing another required option (which is not given > in the docs) or does my NIC lack packet pacing support? > > Thank you very much in advance. > > Best regards, > Carsten > > [1] > https://doc.dpdk.org/api/rte__ethdev_8h.html#a990d8351447a710628cbb24a28d3252d > [2] https://patches.dpdk.org/patch/73742/ > [3] https://doc.dpdk.org/guides/nics/mlx5.html#run-time-configuration > [4] > http://code.dpdk.org/dpdk/v20.11/source/drivers/net/mlx5/linux/mlx5_os.c#L1278 > [5] > http://code.dpdk.org/dpdk/v20.11/source/drivers/common/mlx5/mlx5_devx_cmds.c#L748 > >