> -----Original Message----- > From: Laatz, Kevin > Sent: Thursday, October 11, 2018 9:58 AM > To: dev@dpdk.org > Cc: Van Haaren, Harry <harry.van.haa...@intel.com>; > step...@networkplumber.org; gaetan.ri...@6wind.com; shreyansh.j...@nxp.com; > tho...@monjalon.net; mattias.ronnb...@ericsson.com; Richardson, Bruce > <bruce.richard...@intel.com>; Ciara Power <ciara.po...@intel.com>; Brian > Archbold <brian.archb...@intel.com>; Laatz, Kevin <kevin.la...@intel.com> > Subject: [PATCH v4 05/13] telemetry: add client feature and sockets > > From: Ciara Power <ciara.po...@intel.com> > > This patch introduces clients to the telemetry API. > > When a client makes a connection through the initial telemetry > socket, they can send a message through the socket to be > parsed. Register messages are expected through this socket, to > enable clients to register and have a client socket setup for > future communications. > > A TAILQ is used to store all clients information. Using this, the > client sockets are polled for messages, which will later be parsed > and dealt with accordingly. > > Functionality that make use of the client sockets were introduced > in this patch also, such as writing to client sockets, and sending > error responses. > > Signed-off-by: Ciara Power <ciara.po...@intel.com> > Signed-off-by: Brian Archbold <brian.archb...@intel.com> > Signed-off-by: Kevin Laatz <kevin.la...@intel.com> > ---
Acked-by: Harry van Haaren <harry.van.haa...@intel.com>
