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 A47A4A00C3; Wed, 21 Sep 2022 17:07:08 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 68B164067C; Wed, 21 Sep 2022 17:07:08 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 160ED4014F for ; Wed, 21 Sep 2022 17:07:07 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 760055C0152; Wed, 21 Sep 2022 11:07:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 21 Sep 2022 11:07:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1663772826; x= 1663859226; bh=49WwlSE+V3aa8VDqz5Qmq1kkiOemx25YFl0jHHQxZP0=; b=K WKc0Ohnp2nHwh9Vl0Ps0Op6sMFE9/MGIG2R3dpRqDoWUsvM5Hyv/Q+gDU+4OBPnF cMZO3/AqJer7KSW8vVU+5EaTJs6OLvVdz+CdnPVTGgmtzyb/L3kruy7brRv7Xtzy OG7WPYMTZ9gz9bS47G8pj+Kwfbl5UDHm7RqVlqv+8BIqCb7c3Xv/LfS4fRa6C1F4 ZbvWNgcQ6KrqTfyoG6CpikzNNBgEt3aSsRLy5SycULaygG5v/rr72Eg5CU5ODEoT HrZDpkl1vxcnL6s+1d8RreXD5wF1VcxC6S6mR36cdbdCyx9a/wvqrhgB3r2ybX6v 2+h1ELml+wELVOJCVec2g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1663772826; x= 1663859226; bh=49WwlSE+V3aa8VDqz5Qmq1kkiOemx25YFl0jHHQxZP0=; b=r oh6uzjmpiK3EXHXSFbV1Hm59R/BcBO8TlpFPeqLbvRw7XJXXFs+BiqQxcwodxgQl tkDKkbpN1oMPZEPq38QYtrPQbkZRo6qJHXsj4LopcFgbqzilyIzF1kFtSXTiSaV/ ZAtB7dEVbhqTktXNKBX3YqgI/YhRISVP7n8YwcdWXIyBucZ7IXCdFdkCIRbWjjnv NFPTBqBZhSY9sJKLJePfA6zCsSI8fM+8abIhyvuSFEVUQBh8A6HkgEqOrfr20FQm feRLCLfAD0lhE7GtKA3iUKqKRRGJxul0l09hqRwagMoAsAaOEm2Suitc2WYgj01s 41BCiXfTM3hA5+GVZmx4w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeefuddgkeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 21 Sep 2022 11:07:04 -0400 (EDT) From: Thomas Monjalon To: Jerin Jacob Cc: Felix Moessbauer , dev@dpdk.org, henning.schild@siemens.com, jan.kiszka@siemens.com Subject: Re: [PATCH v6 2/2] Add l2reflect measurement application Date: Wed, 21 Sep 2022 17:07:02 +0200 Message-ID: <3496648.LM0AJKV5NW@thomas> In-Reply-To: References: <20220902084533.675698-1-felix.moessbauer@siemens.com> <20220902084533.675698-3-felix.moessbauer@siemens.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 21/09/2022 16:42, Jerin Jacob: > On Fri, Sep 2, 2022 at 2:16 PM Felix Moessbauer > wrote: > > > > The l2reflect application implements a ping-pong benchmark to > > measure the latency between two instances. For communication, > > we use raw ethernet and send one packet at a time. The timing data > > is collected locally and min/max/avg values are displayed in a TUI. > > Finally, a histogram of the latencies is printed which can be > > One highlevel comment, > > IMO, We don't need to add code for capturing in histogram and analyze > it in C code. > We can simply use, rte_trace and so that we can visualize with > standard trace viewers. > Also add add python based script parse the CTF emitted by trace and find > min/max/avg values to simply the code. +1, let's keep it minimal and simple