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 6BA8D45DCC; Fri, 29 Nov 2024 12:44:57 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0BD74402AE; Fri, 29 Nov 2024 12:44:57 +0100 (CET) Received: from fhigh-b1-smtp.messagingengine.com (fhigh-b1-smtp.messagingengine.com [202.12.124.152]) by mails.dpdk.org (Postfix) with ESMTP id E5C5A4014F for ; Fri, 29 Nov 2024 12:44:55 +0100 (CET) Received: from phl-compute-04.internal (phl-compute-04.phl.internal [10.202.2.44]) by mailfhigh.stl.internal (Postfix) with ESMTP id 405D725400A2; Fri, 29 Nov 2024 06:44:55 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-04.internal (MEProxy); Fri, 29 Nov 2024 06:44:55 -0500 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:subject:subject:to:to; s=fm1; t=1732880695; x=1732967095; bh=NmEf2bagLqu2YC3EwVpqK9lvdKIMKzogVX5SV68VyDo=; b= lkq1rnKcKsZWMNXtsmQTpGpxYu7oOo0UjUAN3iSeMQwLMc1R0x+YnfQRCMpTNbxJ hObEk5wKhpJZc77of45oAwhUfdkiBrCh3EUlscBUctlS1+E4eR5oCGH7cDH5F83a VVyIZ0yuSuTW9IIkel5Ip6uaEfkFGHDvyN4qRgqat5AYPvPHOvACzzNqWC+M4Bqa xADQNFscB5B0ZzY/scuR6NfVGaQTATXjR72PzAA0ZBt4y0DTimHFyeKuwsl0OcaC qHwVjwYOPzKlt9dvcDiPrPrO5iIfjdU31tmRWiZBqgo5nx0nrZYiCt7dVmmvPV2+ 61SxUVZ4rffikmfnbbKWvQ== 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:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1732880695; x= 1732967095; bh=NmEf2bagLqu2YC3EwVpqK9lvdKIMKzogVX5SV68VyDo=; b=P rP7pMk7s3yYbVyH28oErwj3YYzQFdrQEgWGK3k9w9P2KB80cyZlJaJUwrDZ5hY3B DMn2aKNI7Un16gRJ4s1NXwPMUzFCzZ5NHSv3DZjhtyUVOdZr6FrGyLlScbu9rMEy 97sE386N6Q2TAFkpxGlQQ/WQPZma194PE2PV0aErCM45oudEFRgtS5Wj/uVIgCoc EpwGqTuIyPOAj8V1pYmOWs2F5b3s2FPAg7GCI0M5XRhYAoYs7dlTkpcHkSiUPE96 z9tlIIVnPlcqCAVv+JWoWkuoQ09ZV1LnxsjV/7S80dKhSTGQXP9YJT5ovOI/1P0k Jh7n5vHzyqI3tVQWss3Cg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrheefgdeftdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecu hfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlh honhdrnhgvtheqnecuggftrfgrthhtvghrnhepffdtuefhhedvkeelleevffdvlefhleeh vdegtddvvdduueeivedtgfejvddugeefnecuffhomhgrihhnpeguphgukhdrohhrghenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgr shesmhhonhhjrghlohhnrdhnvghtpdhnsggprhgtphhtthhopeegpdhmohguvgepshhmth hpohhuthdprhgtphhtthhopegruggvlhdrsggvlhhkhhhirhhisehgmhgrihhlrdgtohhm pdhrtghpthhtohepuggvvhesughpughkrdhorhhgpdhrtghpthhtohepjhgvrhhinhhjse hmrghrvhgvlhhlrdgtohhmpdhrtghpthhtohepshhkohhrihesmhgrrhhvvghllhdrtgho mh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 29 Nov 2024 06:44:53 -0500 (EST) From: Thomas Monjalon To: Adel Belkhiri Cc: dev@dpdk.org, jerinj@marvell.com, skori@marvell.com Subject: Re: When the trace buffers are saved to disk? Date: Fri, 29 Nov 2024 12:44:52 +0100 Message-ID: <9370936.CDJkKcVGEf@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" 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 28/11/2024 20:17, Adel Belkhiri: > Hi all, >=20 > Recently, while tracing applications from the apps and examples > directories, I became confused about when the trace buffer is written to > disk. Is the trace data saved only when rte_save_trace() is called, or do= es It is rte_trace_save() > it also automatically save when the buffer becomes full? No, DPDK is not doing such thing without user agreement. > From my understanding, rte_save_trace() is invoked when the application > executes rte_eal_cleanup(). Does this mean the target application needs to > explicitly support tracing by calling rte_save_trace()=E2=80=94perhaps at= regular > intervals=E2=80=94to dump the trace buffer to disk? Otherwise, will we on= ly get a > fragment of the trace saved during rte_eal_cleanup() execution? Yes you get it right. > Thank you for clarifying this point. Thanks for asking. If you think the doc below is not clear enough, do not hesitate to submit a patch to make the doc better: https://doc.dpdk.org/guides/prog_guide/trace_lib.html