From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BB7DEA053D; Wed, 5 Aug 2020 17:26:21 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 245FA2C23; Wed, 5 Aug 2020 17:26:21 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 711C22BF2 for ; Wed, 5 Aug 2020 17:26:19 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id CEE975C009C; Wed, 5 Aug 2020 11:26:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 05 Aug 2020 11:26:18 -0400 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; s=fm1; bh=hwEo9Bty2z9vM LkHjuvnvFRM0s4TEQmYlauG+DrwUfk=; b=cApbqmYY0N6Z49Fk3z+ZG4NTfxAhr jT0Dv+xF/ltyxABH+VvKrD1bwbm7wk9LUv8RXV/ROEpOmXb5Mhw6I2aGHkOINS9i sLawCDNAl9yYPuGrGrRGhrXZpyFRzhrEZ7PJYvq9RE9kitz33hqjUgS+K0JGAyLN RH0oq2LBibruOHwSyTfVz1s1CvzOWpq0vVoAIeu/vrg7hyhqkkIsu88UIHty4dpN vf6NBJfiPw+C0Avyi6IXADQSBhYgPQKn/zsxo0d1b1/KFLFtx9pl4mwzDJrAnHpO 8moSYSbUf5T49iUD+YArbx2AKifyx+lI2Ez6qjzDeACIlNC6V2MgMpIMg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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= fm3; bh=hwEo9Bty2z9vMLkHjuvnvFRM0s4TEQmYlauG+DrwUfk=; b=mJJqty1T CX7xcCBkT5d7N/E2kGa3iiQHwDfi0ADNB80GqN6JRthJvBSogrd2lYKmdw1y9Igu tFx2+ah2/JhzdxgYJAojZyUBY3HYPUf05awsnwTf5Hlygqd8GeUtxci5ukWeoW3b zXvw/8YnSwpHyU34n+bYYpj3Mr/U0oZwbbK/AaHD9X/z4lfcbpqFQmb09mkW14SQ 1WO2qHQ8WeNDcN53ervzVWJ2i0UVYprc7uD+83tQfdcJ1VolQWbOBIZMNppSm8vT wI5MfNNTEIz9lLcdYTLfMulWvkgD0vELFu529A6y40hchwaC/O4rUFYeCgIx1A4U w1ZBPg2JwlRDTA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrjeekgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkofgjfhgggfestdekredtredttdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedvhefgiedvjeegtdevheefhfetleefgfeivefgffevfeejgedtgfeu tdehtdegveenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth X-ME-Proxy: Received: from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 96E2E3280065; Wed, 5 Aug 2020 11:26:17 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: Viacheslav Ovsiienko Date: Wed, 5 Aug 2020 17:26:10 +0200 Message-Id: <20200805152610.277087-1-thomas@monjalon.net> X-Mailer: git-send-email 2.27.0 In-Reply-To: <1595865064-12892-1-git-send-email-viacheslavo@mellanox.com> References: <1595865064-12892-1-git-send-email-viacheslavo@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH v3] doc: add timestamp upper limitation in mlx5 guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" From: Viacheslav Ovsiienko Add description about Tx scheduling timestamp upper limit. If timestamp exceed the value, it is marked by PMD as being into "too-distant-future" and not scheduled at all (is being sent without any wait). Signed-off-by: Viacheslav Ovsiienko Signed-off-by: Thomas Monjalon --- v2: typo fix v3: more typos fixed and small rewording --- doc/guides/nics/mlx5.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index 90202c0bbb..211c0c5a6c 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -253,6 +253,14 @@ Limitations reported via device xstats to assist applications to detect the time-related problems. + The timestamp upper "too-distant-future" limit + at the moment of invoking the Tx burst routine + can be estimated as ``tx_pp`` option (in nanoseconds) multiplied by 2^23. + Please note, for the testpmd txonly mode, + the limit is deduced from the expression:: + + (n_tx_descriptors / burst_size + 1) * inter_burst_gap + There is no any packet reordering according timestamps is supposed, neither within packet burst, nor between packets, it is an entirely application responsibility to generate packets and its timestamps -- 2.27.0