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 DF84B45DD1; Fri, 29 Nov 2024 22:23:33 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ABA2F4027D; Fri, 29 Nov 2024 22:23:33 +0100 (CET) Received: from fout-a1-smtp.messagingengine.com (fout-a1-smtp.messagingengine.com [103.168.172.144]) by mails.dpdk.org (Postfix) with ESMTP id 986C240150 for ; Fri, 29 Nov 2024 22:23:32 +0100 (CET) Received: from phl-compute-11.internal (phl-compute-11.phl.internal [10.202.2.51]) by mailfout.phl.internal (Postfix) with ESMTP id 168041380236; Fri, 29 Nov 2024 16:23:32 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-11.internal (MEProxy); Fri, 29 Nov 2024 16:23:32 -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=1732915412; x=1733001812; bh=qquJsltjf73D5YNgFIogcfJ7mkOUIlKVXgAWnd3d9zE=; b= k1l0r6R29zC8I2bG2YoJmVXJRxPnVdl1WFrOhB//PLfXVmNm1qkG6PDsQrMfvLSR wte4yLSrFimBP9LjKCEiZtmvyPUE86oRsgfTYh3aDIyKbm6BAg2w3VnHDXTb4ZHk bXfT+2NlRw00pHeqPMAU5/aIaDXLBjhb+k1U/GXNIMJwz0ptDjUwmTHMGrM8weRB 7NL0couOwlLgl/PD8shNZKzHDze7rOwzNO752iIBKPnPGZOJysDj6qFEvW+jLX+P tm2gkJ8q3YfHNBXfAWfJL5sw72SKNtfTONg8H4UrRYrGsd06FK//Py1ANalvHhs7 eZkhQaxmySP6ut9/HYAFPQ== 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=1732915412; x= 1733001812; bh=qquJsltjf73D5YNgFIogcfJ7mkOUIlKVXgAWnd3d9zE=; b=C e20XhjVWQ8iMQN33CEiFV/5jzj02qCVuTbI6BMtXGCF2Ea7Bg9ebtWjFWiKFGwla CDKeeIG9Drmu85EOCx4q4bCTr8Lwb77vgzj8OjI0vgruMJ7DRKGkVC/zwsXtSm5p lctEm0f3lu1fKruyw6bGECANba8GGWX2Y4maCf6PK/CkmtUew87SNUCQL74KpAj/ 0UXPrOMEWJymD4ip8yz4jE9iWl2In9vhwWm1pEYlQWElawRL4L+kNbGbhIXju1Vz zBswG6InCftOdGh9XpbslV7d6WyzaQ+HvTsWzapMsB6B4oTj7ddQj5x4cZQTDb4f KTpd4yYeRukoLUDiE5Vag== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrheefgddugeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhephffvvefufffkjghfggfgtgesthhqredttddtjeen ucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrg hlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpefftdeuhfehvdekleelveffvdelhfel hedvgedtvddvudeuieevtdfgjedvudegfeenucffohhmrghinhepughpughkrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhm rghssehmohhnjhgrlhhonhdrnhgvthdpnhgspghrtghpthhtohepgedpmhhouggvpehsmh htphhouhhtpdhrtghpthhtoheprgguvghlrdgsvghlkhhhihhrihesghhmrghilhdrtgho mhdprhgtphhtthhopeguvghvseguphgukhdrohhrghdprhgtphhtthhopehjvghrihhnjh esmhgrrhhvvghllhdrtghomhdprhgtphhtthhopehskhhorhhisehmrghrvhgvlhhlrdgt ohhm X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 29 Nov 2024 16:23:30 -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 22:23:28 +0100 Message-ID: <1953300.taCxCBeP46@thomas> In-Reply-To: References: <9370936.CDJkKcVGEf@thomas> 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 29/11/2024 21:39, Adel Belkhiri: > Thank you for the clarification, Thomas. Indeed, the documentation for the > trace library is kind of limited. If you don't mind, I have another > question: Would it be useful to have an API to register a callback (to sa= ve > trace data) when the buffer is full? I suppose yes, the problem being which thread is running file writing. I leave it to the maintainers of the trace library. > On Fri, Nov 29, 2024 at 6:44=E2=80=AFAM Thomas Monjalon wrote: > > 28/11/2024 20:17, Adel Belkhiri: > > > Hi all, > > > > > > 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 > > does > > > > 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 applicati= on > > > executes rte_eal_cleanup(). Does this mean the target application nee= ds > > to > > > explicitly support tracing by calling rte_save_trace()=E2=80=94perhap= s at regular > > > intervals=E2=80=94to dump the trace buffer to disk? Otherwise, will w= e only 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