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 349F2A0521; Tue, 3 Nov 2020 17:20:30 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7C453AC8F; Tue, 3 Nov 2020 17:20:28 +0100 (CET) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by dpdk.org (Postfix) with ESMTP id 04316AA06 for ; Tue, 3 Nov 2020 17:20:26 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 8418BE22; Tue, 3 Nov 2020 11:20:24 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 03 Nov 2020 11:20:25 -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=fm2; bh= Yq6gHdEmreVKfvIWIYnePvJpOTNojpXLT6dYYIg5ns4=; b=Xje9MlyzgI56sAfh KpEwNbywrLlpb2W7Gi4tz0bZ+UvHa4O0108cjhWdVwLMYdb/ZHJ0qxnd/+UEpkLy uGfQH7llun6E6xX8KuRSmiFS5TRM8VSpu+LSA/QVNGIxJFtf2bQWqtCbEdjf3+it WK1gt15fTZVSD6dvrBRlWQB0HeaWhkyEhS4NKTOtQTExcHYfCzS1bNu0PtNA1jo1 Y+U6/XOQqT6twp1HVv2/jAJcSEO1N5Ck4PgfkQJRlPykDCzhFAQ/aaKmIDBQgKhx 1XW9DwgoToY0911IPWKx3n2lneizRrwxeYIjN01xJNAprjIRUu+wgo3VF7sNrevc yLe5Mg== 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=Yq6gHdEmreVKfvIWIYnePvJpOTNojpXLT6dYYIg5n s4=; b=U4Ukg4n4gXiH1k9mSoFwew/YZtHd0PA22cGOgROkOsztlOvJet2s2BKwr Cuy+7H4UUkgMEXgF1N2REh8IIH32zZuOoUo7wt35yL8aRMW/GwFSdEZOwEppdIKM j0SM6ptZWjCYE5X5u1eZl+7yFqinmvyygIlTNWSLL23aOasUbVVSUqjbLceSYMWB uxq+359V+oPlvJ5qjda+KzIxH2QSlEDlUmIXhqf/zwz+aoFrcRU1fbyCrrtOdnx0 Qx6FlRx6TWc1hJv0tziYcTD720SZjQFUAf8vH5T8oy6hO92GUO7tVxcgumfPgy/7 9XlP2nvQwL9FrRAAqFqnl+D+HjSkw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddtfedgkeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepffdvffejueetleefieeludduuefgteejleevfeekjeefieegheet ffdvkeefgedunecuffhomhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrd dvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 170763280059; Tue, 3 Nov 2020 11:20:22 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, ferruh.yigit@intel.com, david.marchand@redhat.com, bruce.richardson@intel.com, olivier.matz@6wind.com, andrew.rybchenko@oktetlabs.ru, jerinj@marvell.com, viacheslavo@nvidia.com Date: Tue, 03 Nov 2020 17:20:20 +0100 Message-ID: <35654921.Wzvq2zENnk@thomas> In-Reply-To: <20201103080839.4d7d50ab@hermes.local> References: <20201029092751.3837177-1-thomas@monjalon.net> <20201103140931.488700-1-thomas@monjalon.net> <20201103080839.4d7d50ab@hermes.local> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v5 00/16] remove mbuf timestamp 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" 03/11/2020 17:08, Stephen Hemminger: > On Tue, 3 Nov 2020 15:09:15 +0100 > Thomas Monjalon wrote: > > > The mbuf field timestamp was announced to be removed for three reasons: > > - a dynamic field already exist, used for Tx only > > - this field always used 8 bytes even if unneeded > > - this field is in the first half (cacheline) of mbuf > > > > After this series, the dynamic field timestamp is used for both Rx and Tx > > with separate dynamic flags to distinguish when the value is meaningful > > without resetting the field during forwarding. > > There should be a place in documentation which describes all the > dynamic fields and their meaning. For example, which drivers/features > set the field and the exact meaning. A dynamic field can be registered by anyone, including the apps. So you will never get a full list. The meaning of each field should be defined in its context (driver, lib or app). > Is the timestamp in HW units, UTC units, or TSC ticks? The timestamp unit is driver-specific. It is explained in ethdev API: http://doc.dpdk.org/api/rte__ethdev_8h.html#a4346bf07a0d302c9ba4fe06baffd3196