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 B1314A0C41 for ; Tue, 30 Nov 2021 17:43:00 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ABB3D41142; Tue, 30 Nov 2021 17:43:00 +0100 (CET) Received: from smtp-relay-internal-1.canonical.com (smtp-relay-internal-1.canonical.com [185.125.188.123]) by mails.dpdk.org (Postfix) with ESMTP id B9355410F7 for ; Tue, 30 Nov 2021 17:42:58 +0100 (CET) Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 5EB613F044 for ; Tue, 30 Nov 2021 16:42:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1638290577; bh=A9X2rpGhjRwD/Q/KUTpN3MxS119gphTYBNiiaG88bGQ=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=XE40Ynl1Ix5H+gjb5thrKTqoTb/D9FBZULflfFMqkUaRsnijQzRPNRa6JIamNHkpT CSgPkd2MDtSeerDJx9UrSukSgGXX+0fR7zaGM5i9G7SsN5/hniYlFoTBXCvx7xe64t NiSG6XD6zZfrBG3PJzjxIn+mw7layxEGLLCtp1T+NtCp8/5rqFSFrFsK1mGiNdccwK jrHGgR0E+4aa9MC16TPZN4Oio23bJ0cxRApM5tNoCB1HZBN8VrWuQAaXh9HbsgDlWR mBL7R+Lv3b/vRLX1zDXvJpVTWKaDSmv+hh0w24jB/UonjONAgJrXLxYC/csDPtqI1m UAYNdO0kPk7zQ== Received: by mail-ed1-f71.google.com with SMTP id t9-20020aa7d709000000b003e83403a5cbso17499171edq.19 for ; Tue, 30 Nov 2021 08:42:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=A9X2rpGhjRwD/Q/KUTpN3MxS119gphTYBNiiaG88bGQ=; b=rClJT6+ojmY3Nj3Jdw/xVAz77Z2knArdNGquUSDMnfWRhyjosEXcboEurb1yZafxKk rv9q27r1dg3ObO/fTeZ0713JD3CdqT5HKP5osueFPiiqt5hi0r3tpwlDzUOuROeREXeg qyWDUkJMo+OHK2kvlvMk0wL3vKnE+SBKFmPIkZCc7lKzrYr6tSmLUR9r4Zc8cyoZdd5u viFBDLEjHfN30LPEnqtjsIpJOex1P8aWGOXIirUWQdEdeJzqWC9Hsu5C2rNHLlMQHKUm 3PC2z8JOm46658QVP9+oLKSH4s+soyt9b8ePPmhP6ZeEay6/52X2Fu29ZLucxXsVp2+S 1xbg== X-Gm-Message-State: AOAM531BaV/JjaSTYKjOoPv6XKSGIrZZuRYBz/F9CN9IWCXCd/68K8CE jDPY4NWg1+Tof8si31rmLGQOLbActvxNCGJBQGTxRK3wXz/PXy6UfVj9ExOxA3/DBxTcB7sLpHJ iVSW7++aOzxdD5638m0YliJGV X-Received: by 2002:a50:ee96:: with SMTP id f22mr86302edr.77.1638290577099; Tue, 30 Nov 2021 08:42:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJyJDO8WacjkPV1vteEUgXHmprYA7pBTtmAIh/pCzpuP6bentPSeBRmlp+AEs5wX0p2c+9JLeA== X-Received: by 2002:a50:ee96:: with SMTP id f22mr86283edr.77.1638290576937; Tue, 30 Nov 2021 08:42:56 -0800 (PST) Received: from localhost.localdomain ([2001:67c:1560:8007::aac:c4ad]) by smtp.gmail.com with ESMTPSA id c8sm11188092edu.60.2021.11.30.08.42.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 Nov 2021 08:42:56 -0800 (PST) From: christian.ehrhardt@canonical.com To: Viacheslav Ovsiienko Cc: dpdk stable Subject: patch 'doc: describe timestamp limitations for mlx5' has been queued to stable release 19.11.11 Date: Tue, 30 Nov 2021 17:35:35 +0100 Message-Id: <20211130163605.2460997-131-christian.ehrhardt@canonical.com> X-Mailer: git-send-email 2.34.0 In-Reply-To: <20211130163605.2460997-1-christian.ehrhardt@canonical.com> References: <20211130163605.2460997-1-christian.ehrhardt@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 19.11.11 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before December 10th 2021. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/cpaelzer/dpdk-stable-queue This queued commit can be viewed at: https://github.com/cpaelzer/dpdk-stable-queue/commit/df4b9cae885a3da71b437fbb5f67c8da10a10dc1 Thanks. Christian Ehrhardt --- >From df4b9cae885a3da71b437fbb5f67c8da10a10dc1 Mon Sep 17 00:00:00 2001 From: Viacheslav Ovsiienko Date: Mon, 8 Nov 2021 18:41:01 +0200 Subject: [PATCH] doc: describe timestamp limitations for mlx5 [ upstream commit 1a3709c1f021afbe58db4a27a179127e561fe401 ] The ConnectX NIC series hardware provides only 63-bit wide timestamps. The imposed limitations description added to documentation. At the moment there are no affected applications known or bug reports neither, this is just the declaration of limitation. Signed-off-by: Viacheslav Ovsiienko --- doc/guides/nics/mlx5.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index e81875de50..6deea36537 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -227,6 +227,20 @@ Limitations - Rx queue with LRO offload enabled, receiving a non-LRO packet, can forward it with size limited to max LRO size, not to max RX packet length. +- Timestamps: + + - CQE timestamp field width is limited by hardware to 63 bits, MSB is zero. + - In the free-running mode the timestamp counter is reset on power on + and 63-bit value provides over 1800 years of uptime till overflow. + - In the real-time mode + (configurable with ``REAL_TIME_CLOCK_ENABLE`` firmware settings), + the timestamp presents the nanoseconds elapsed since 01-Jan-1970, + hardware timestamp overflow will happen on 19-Jan-2038 + (0x80000000 seconds since 01-Jan-1970). + - The send scheduling is based on timestamps + from the reference "Clock Queue" completions, + the scheduled send timestamps should not be specified with non-zero MSB. + Statistics ---------- @@ -839,6 +853,10 @@ Below are some firmware configurations listed. FLEX_PARSER_PROFILE_ENABLE=0 +- enable realtime timestamp format:: + + REAL_TIME_CLOCK_ENABLE=1 + Prerequisites ------------- -- 2.34.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2021-11-30 16:50:13.533034998 +0100 +++ 0131-doc-describe-timestamp-limitations-for-mlx5.patch 2021-11-30 16:50:05.966874821 +0100 @@ -1 +1 @@ -From 1a3709c1f021afbe58db4a27a179127e561fe401 Mon Sep 17 00:00:00 2001 +From df4b9cae885a3da71b437fbb5f67c8da10a10dc1 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 1a3709c1f021afbe58db4a27a179127e561fe401 ] + @@ -14,2 +15,0 @@ -Cc: stable@dpdk.org - @@ -22 +22 @@ -index d175c2061e..552e06c0db 100644 +index e81875de50..6deea36537 100644 @@ -25,3 +25,3 @@ -@@ -480,6 +480,20 @@ Limitations - - - Needs OFED 5.4+. +@@ -227,6 +227,20 @@ Limitations + - Rx queue with LRO offload enabled, receiving a non-LRO packet, can forward + it with size limited to max LRO size, not to max RX packet length. @@ -46,3 +46,3 @@ -@@ -1242,6 +1256,10 @@ Below are some firmware configurations listed. - FLEX_PARSER_PROFILE_ENABLE=4 - PROG_PARSE_GRAPH=1 +@@ -839,6 +853,10 @@ Below are some firmware configurations listed. + + FLEX_PARSER_PROFILE_ENABLE=0 @@ -54,2 +54,2 @@ - Linux Prerequisites - ------------------- + Prerequisites + -------------