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 DF38EA0524; Wed, 5 May 2021 11:37:20 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A9B4A40040; Wed, 5 May 2021 11:37:20 +0200 (CEST) Received: from mail-il1-f179.google.com (mail-il1-f179.google.com [209.85.166.179]) by mails.dpdk.org (Postfix) with ESMTP id 81BE84003C for ; Wed, 5 May 2021 11:37:19 +0200 (CEST) Received: by mail-il1-f179.google.com with SMTP id h6so1185577ila.7 for ; Wed, 05 May 2021 02:37:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=mlPWXyWVf1BitiDlLHZmPfepySQ9a4ZdR0ndYCJzpZY=; b=j8fk8pX3a/Op5DE//C0AmCI6EB32v3Df1a9ju/alOYjoW4Y+hIYVUsT4JH31kL5Doi Y2ENDWsvMFZRshbQgc22ZdGwqU84o7AUKZvR/+UfzuEyPjD/kaZGZY9GvFIYJI211bcs VbIrK1aeat/yvGj1zE/vW7FF0g1YkPme+c3X9TWaWlQxiSQxQlK82Svxfj+M66xJ4mLP lyzRqqXY3D1IDd0z8xIzQ9wT7XPgDmkn0u+1ZwsaPtR7uM8/tSWshCW1quKF504VN90a et472cxoX3IE+CtkYtF4uSzs9lS8X5uSk2g5A+dsMjbXhRLNoWm7fVjkVf4yR9CDjAU8 htWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=mlPWXyWVf1BitiDlLHZmPfepySQ9a4ZdR0ndYCJzpZY=; b=IdHzyt0YmQPsL20tndA+iNZqHBpcxgIzS3s1Fhqywt3Qr5C4zlNBlH53hJGrbHXDNa UtpiYWhEh5jP+fGbxi9hHBOrH4ZY3dRJ9C9vGT0X/4FHmaKZgyn73SJbcKef0Vf2RY+U 0hBYx76I7NHVSCDHDk7R94G1NUfcRRDRQ8ifYkteHECEdWyDnDdxFUFyeXYPGnQgR2zI A68RQ3D2KPBcCBm1gkGxCWcAjkG6buZ8XkeYx8D5FFxzX8Core4obY6bIYR5vFY8hTCt +4+6F8Y/r7fUs+G50x7l4Bs1HaiWnNrZNnlwrW40EbWxsO9duSivJaSg2mMdV+AdtFUD V9QQ== X-Gm-Message-State: AOAM531v4BI9M9CLkOYOgWGA0Qfbw+VT36jyq9pqo0G7p8+mPqnBWdXo w7qEBn2vfg6mzlcycTUcPiBeArjbtGCAvSyDFH4= X-Google-Smtp-Source: ABdhPJw8O+hTB/GWnOlP+OuplZnHhuAKLp0DTYo3TPBmuZAmYBoClccPu3cejBp/Jmi/QIdrbGgB4sP6HekDvKwkgJY= X-Received: by 2002:a05:6e02:e43:: with SMTP id l3mr25272257ilk.130.1620207438915; Wed, 05 May 2021 02:37:18 -0700 (PDT) MIME-Version: 1.0 References: <8309999.7OePmkgMO5@thomas> In-Reply-To: <8309999.7OePmkgMO5@thomas> From: Jerin Jacob Date: Wed, 5 May 2021 15:07:02 +0530 Message-ID: To: Thomas Monjalon Cc: Harman Kalra , "bruce.richardson@intel.com" , "kevin.laatz@intel.com" , David Marchand , "stephen@networkplumber.org" , "dev@dpdk.org" , Luca Boccassi , Jerin Jacob Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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" On Wed, May 5, 2021 at 2:13 PM Thomas Monjalon wrote: > > 05/05/2021 09:49, Harman Kalra: > > Hi All, > > > > We have a use case where we need to gather statistics over network. Cur= rent 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 decis= ion to run library with network sockets by passing respective eal flags. > > 2. We can introduce some key/password authentication mechanism to the l= ibrary, where only authorized clients can get connected to the server. Pass= word 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. ZeroMQ is a good option for Transport to hide the underlying transport variants like In-process, Intra-process, TCP. Also, it has various different options for security backend like http://curvezmq.org/ if we pick ZeroMQ for transport then it will translate to 1) Remove unix file socket from telemetry 2) Use ZeroMQ for local and remote messaging 3) Needs to make telemetry or dpdk depends on ZeroMQ library(Since telemetry is experimental, I hope, we can change this) Thoughts from others including telemetry maintainers > > 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 c= ollect driver stats? Is this upstream able? > > >