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 2970A42C99; Mon, 12 Jun 2023 20:04:05 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BAA6340698; Mon, 12 Jun 2023 20:04:03 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 430F440689 for ; Mon, 12 Jun 2023 20:04:02 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id D6CB15C0077; Mon, 12 Jun 2023 14:04:01 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 12 Jun 2023 14:04:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1686593041; x=1686679441; bh=hNyYplg2+pk/hs2M8eisO9RnZUxBnTBBIEK m4/z6TT4=; b=Uvzp5C7+1cDmuHgsjbl0ZywgPyUIlK46adYzo/IGPUgnl90fstG +pmnuhYSzh4auU9zc8q3k9IcLRHEK6KWUACUCkgB+9Ff3dyBrmHnN/7qpWSb7Qdv zUbr5WTAHZ26NubU3xospyFqjUnz9a9Ehh9An9MRWKhcTQYKfSSFoe1jxNlkQkQP NMHK1W3Ya6mMf518bVz7KTybPv9DZCg4urT77k+NAaNMuSk6LBbHSVTjOrddU+X0 05KAGdZ+v5kBzLJgP7RQuNQgo50C7Ds6tSEchO+09kymvj1ktO+GljqJKXl5SvIU ZvfpmzoCzhNL3kbM2z3NU3KJ8b9tzZlfNOA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1686593041; x=1686679441; bh=hNyYplg2+pk/hs2M8eisO9RnZUxBnTBBIEK m4/z6TT4=; b=KGFjnd4nLameyH52NxRV9mbKDvfcXDDJBnMtQKXUUjkVCJgEMml CjzzuiKXr/hLrRfOoMrlD1QFOSdkEQw1G1LTjh1aj/hhhc4p+ikZ9RvFfi1QRLWy kdIALjuhJ++Dsw+sDNqXzrQ1pYsBoPmDADdZk5lR6/IWJ8qMUFRudpXeOu2SQ7Rr TYUH2rl20Z8yTx3lLhV06jweSRQ8m9tnbPK5LhxZu1SaXcLN55z2Zx71B8keaoMz UjgUjcUkXPMdTztZ31tnM5c0e5NXFMQaQwMG1ZSH9Y+xNFdLitqbvUCaf8axZQw3 TqdAJr+sNLWkChKqnKmfRwgX6Y74lN2kZoA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgeduhedguddvtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddt ieekgfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 12 Jun 2023 14:04:00 -0400 (EDT) From: Thomas Monjalon To: Viacheslav Ovsiienko , rasland@nvidia.com Cc: dev@dpdk.org Subject: Re: [PATCH] net/mlx5: add timestamp ascending order error statistics Date: Mon, 12 Jun 2023 20:03:59 +0200 Message-ID: <6914095.18pcnM708K@thomas> In-Reply-To: <20230420081835.19927-1-viacheslavo@nvidia.com> References: <20230420081835.19927-1-viacheslavo@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 This patch is marked "Awaiting Upstream" in patchwork, but it doesn't seem merged anywhere. Please check its status. 20/04/2023 10:18, Viacheslav Ovsiienko: > The ConnectX NICs support packet send scheduling on specified > moment of time. Application can set the desired timestamp value > in dynamic mbuf field and driver will push the special WAIT WQE > to the hardware queue in order to suspend the entire queue > operations till the specified time moment, then PMD pushes the > regular WQE for packet sending. > > In the following packets the scheduling can be requested again, > with different timestamps, and driver pushes WAIT WQE accordingly. > The timestamps should be provided by application in ascending > order as packets are queued to the hardware queue, otherwise > hardware would not be able to perform scheduling correctly - > it discovers the WAIT WQEs in order as they were pushed, there is > no any reordering - neither in PMD, not in the NIC, and, obviously, > the regular hardware can't work as time machine and wait for some > elapsed moment in the past. > > Signed-off-by: Viacheslav Ovsiienko