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 CB1F1A0524; Wed, 5 May 2021 10:43:41 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4FEB240040; Wed, 5 May 2021 10:43:41 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by mails.dpdk.org (Postfix) with ESMTP id E36384003C for ; Wed, 5 May 2021 10:43:39 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 63A3E13A3; Wed, 5 May 2021 04:43:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 05 May 2021 04:43:39 -0400 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=fm1; bh= 8muaU3o0rvNUsBiujm3VKZjBxPATO8I/6DlWcoZLM2c=; b=1hwtp899VoYKa15M gJP4dy+IZRE3TSNyfM+vbefRkJEYtM9PZgq6FezShW69pVyHE+B1yun2Amb71pBc vsoq4UJss9wLCJemc6Q3Mwn9tzboBBcG/Ucmdp7kTvwxglEGuJKqM2wCGXqrFQqX k9XTsLMtbak3XQdkOdqEHydoINruxV4U6sUoJqcAgN1RmGSnrm1OQ9OYubkv6LCB BZvwwJ0way1smmlyJYiyfco8apZuuGzwtdJ15fv63yxPjMs18WWDvEOFUduz6EqT KOP45+hrbQmQZe8zrfBdsW123IbNTdcosorH1CsVjk/Qu+wQAF5gM9lmxzOfslO1 /w8mgQ== 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=fm2; bh=8muaU3o0rvNUsBiujm3VKZjBxPATO8I/6DlWcoZLM 2c=; b=cxGDmUmJpEPySU1e7PSGWiPRvVsJ0mYyhtLSMxF0HVvQm19U2dYJxfarO LkUaEDbUR2X36jy2PBTnyBVrC9xHRMhldzD51NqSsiOwCLsbTQ5og2imAfHMhPoY cpoCpG/o5EnjotCbpx7AY/h4yRytu2CoXbQ877JcykRroJr1OiO/tQCGUgQXcgE4 1ZX0CHwIHAKZv+QHBGGvdFlxIDuUmC0hqJw8W4w8eLEk+SPqF+wqEWvE6LwLS3yH C3yVKC4Rpz0YgunsP4tEUYkuo/6aa5ZBr4zTmOCvBnI84t/Vd9MPCro4oX2kkl94 Ht1NjUvlBEJ4UBLomayACqpmypjbQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdefkedgtddvucetufdoteggodetrfdotf 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; Wed, 5 May 2021 04:43:36 -0400 (EDT) From: Thomas Monjalon To: Harman Kalra Cc: "bruce.richardson@intel.com" , "kevin.laatz@intel.com" , David Marchand , "stephen@networkplumber.org" , "dev@dpdk.org" , bluca@debian.org, jerinj@marvell.com Date: Wed, 05 May 2021 10:43:34 +0200 Message-ID: <8309999.7OePmkgMO5@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] DPDK Telemetry library enhancement 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" 05/05/2021 09:49, Harman Kalra: > Hi All, > > We have a use case where we need to gather statistics over network. Current implementation of telemetry library is based on Unix socket, we would like to enhance the scope of library to use network sockets. We understand security challenges with network sockets, to overcome them can we can think of two steps: > 1. By default library will be using Unix sockets, it will be user decision to run library with network sockets by passing respective eal flags. > 2. We can introduce some key/password authentication mechanism to the library, where only authorized clients can get connected to the server. Password can be passed by the user as eal flags, something similar to vf token which is uuid based. > Kindly provide us suggestions/challenges over this enhancements. Not sure it should be part of the telemetry lib. In any case, when implementing network communication, I encourage you to look at ZeroMQ. It reminds me this discussion for IF proxy: http://inbox.dpdk.org/dev/2580933.jp2sp48Hzj@xps/ > > One more query, can we register driver specific telemetry commands to collect driver stats? Is this upstream able?