DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Harman Kalra <hkalra@marvell.com>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	 "kevin.laatz@intel.com" <kevin.laatz@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	 "stephen@networkplumber.org" <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>, Luca Boccassi <bluca@debian.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] DPDK Telemetry library enhancement
Date: Wed, 5 May 2021 10:57:37 +0200	[thread overview]
Message-ID: <CAJFAV8yX0s5tR3Dd_rytS4hByS9eNiWtQvquO4gALU7e2Xb=uA@mail.gmail.com> (raw)
In-Reply-To: <BN9PR18MB42041A43A2481A77E3C947F2C5599@BN9PR18MB4204.namprd18.prod.outlook.com>

On Wed, May 5, 2021 at 9:49 AM Harman Kalra <hkalra@marvell.com> wrote:
> 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.

Rather than implement a new protocol, and code a new client, would
collectd fulfill your need?

Info currently retrieved by the telemetry collecd plugin is hardwired.
Maybe some configuration could be added to this plugin for your new stats.


>
> One more query, can we register driver specific telemetry commands to collect driver stats? Is this upstream able?

I don't remember a limitation/guideline on this subject.
Any command can be registered, this is up to the telemetry client to invoke it.


-- 
David Marchand


  parent reply	other threads:[~2021-05-05  8:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05  7:49 Harman Kalra
2021-05-05  8:43 ` Thomas Monjalon
2021-05-05  9:37   ` Jerin Jacob
2021-05-05 10:01     ` Bruce Richardson
2021-05-05 10:14       ` Jerin Jacob
2021-05-05  8:57 ` David Marchand [this message]
2021-05-05 10:05   ` Bruce Richardson
2021-05-05 10:06   ` [dpdk-dev] [EXT] " Harman Kalra
2021-05-05 11:26     ` David Marchand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJFAV8yX0s5tR3Dd_rytS4hByS9eNiWtQvquO4gALU7e2Xb=uA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.laatz@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).