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 A6B39A0A05; Tue, 19 Jan 2021 22:52:09 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 21154140EDB; Tue, 19 Jan 2021 22:52:09 +0100 (CET) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by mails.dpdk.org (Postfix) with ESMTP id 71125140EAF for ; Tue, 19 Jan 2021 22:52:07 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id B5D9511F4; Tue, 19 Jan 2021 16:52:05 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 19 Jan 2021 16:52:06 -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=fm3; bh= wgtDfUE98xUiMSJpqVr1dpYXtbA59t1lInmFRCOHOpk=; b=dQIoWrm3BG3RhXOA 9BIxpBr+r9+v4G3PtijK1iXvXKduttLbIH1aMR97oFaSox7/xDYAC/7jDMumDq8f bWKlba5o6xbzQIt5YSyZ3dMqA3Rv74K+agUhFDE0r4s9cxKCevR9MtDBVQwDPIOB h5QxaWDyVTJfUaba1dr/KE2huNAQu6gGRT2BtsbMw7jIQxOm1bKv+oLDCkaBKg6u 99HuMHFmQn6hruq/C0jD7vElfux1linHNsXMFIFQ8zFHYGa/EHkS80jqKC7+9FRM mQO0qovDy/ZZmOaw6ezGQnsYQgvTRX7sDLm9IXqRNtG/eKFvqGbRoU6NPwhtaIwD 9R0ioA== 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=wgtDfUE98xUiMSJpqVr1dpYXtbA59t1lInmFRCOHO pk=; b=nM5o0YmCd8KWV3KH9gl8L58nWbPUJRAjP04w2dWVOnkYqIgJvcl5yctTo Nd3jHlRQaq+fHUk6D5Z5sLAHT2XM6W0D9rxlF4k4uqus/BQBoCUXkjjZwDcbp6kh uSDF1zYL6ajiiUyqqhWYcCk2QtX6Mbas2+o7PM1GU028S4BvHFA1tlUE3IqbjF0/ wPdlUV7YD9jqwsmHerYpM+7BS/EcNY2EJq/wreceKH2KcB94wJd/cqNEPfgQ9fe4 9Diq7Wg5y2IOffRCWbisgovl0yMPVOYll0X9LDLqXUpicb15eKNU0bZzE498bTKr 5Fg/VtEBMb2K3GKhRSt/o1fn6rNcA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddtgdduheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpedugefgvdefudfftdefge elgffhueekgfffhfeujedtteeutdejueeiiedvffegheenucfkphepjeejrddufeegrddv tdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 1B1EF240065; Tue, 19 Jan 2021 16:52:04 -0500 (EST) From: Thomas Monjalon To: Tyler Retzlaff Cc: dev@dpdk.org, dmitry.kozliuk@gmail.com, navasile@linux.microsoft.com, ciara.power@intel.com, bruce.richardson@intel.com Date: Tue, 19 Jan 2021 22:52:03 +0100 Message-ID: <5601419.A6MszWdEHB@thomas> In-Reply-To: <20210119213125.GA1983@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <1610408246-29482-1-git-send-email-roretzla@linux.microsoft.com> <4843599.5pFrObeWOY@thomas> <20210119213125.GA1983@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] metrics/windows: build rte_metrics library 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 Sender: "dev" 19/01/2021 22:31, Tyler Retzlaff: > On Sun, Jan 17, 2021 at 11:19:55PM +0100, Thomas Monjalon wrote: > > > > Not sure it makes sense without the new telemetry feature. > > Please focus on telemetry lib instead of half-enabling > > the old metrics lib. > > > > can you elaborate? (or reference a mailing list discussion) that gives some > guidance? > > is the telemetry lib a replacement for metrics? the component we have now > relies on the non-telemetry functions exported from metrics but does not > use the telemetry functions. > > also, i notice that the meson.build for telemetry lib has an include path > that references rte_metrics but does not appear to actually include any of > the headers from rte_metrics (vestigial? missed in previous cleanup perhaps?) I think Bruce and Ciara will better explain than me the intent of the telemetry lib and the compatibility path with the metrics lib.