From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 8BB074CE4 for ; Wed, 24 Oct 2018 16:13:01 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2245C21FEA; Wed, 24 Oct 2018 10:13:01 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 24 Oct 2018 10:13:01 -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=mesmtp; bh=JvzPHDU6Z9O4SbpWDQmOcCe49WXmVX2kt4Xh8m2P09E=; b=LNIFYcdKShDz 26e7YNK/MjFSf70791DC/Sig+I9U+xRnt6rUYmrl0Uh/+3WVZgg3oYUEhYyOOhCa 4x6H2Mzw+1VFpU9TEQnBr0seHcipLHqxe4cqMvCWS6yZc0JLyw8yTbKaCEBFhto8 tYckAy1dKowZiNXw1Z9Hs2BbUNhQZiA= 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=JvzPHDU6Z9O4SbpWDQmOcCe49WXmVX2kt4Xh8m2P0 9E=; b=LD24rvSXw9RQ/ppTKm/iIhgpsdmUNhkRezyo3WASVEBXWA0mmnXR/+Qiy 2SXRUV/wNRQ4Kk8Ww4GknY/NBptmePiGyprGW3KkU17sVKu979Tzcqg+2UL/OCsy 6a9s2zZAzKmaFKHCkji8IE/6PSVdgE2TW+lBgZDddvwlQcKAnzw3refW5jtzYXO7 qdU4k9LdTGJMrd1C1FbJVvihsCvTdPZn451ftfzca9kJ5cgJ6DWgXwtbnnULT5hG 0f1CzOYwvTBFqjZfHnjqtbmUX2IzyhZTrohD7Vbv1gw6rfKa/z1t64CPnaPNGema evEsTeQTMxUDrbHZg9CHdmlN/NVXw== X-ME-Sender: 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 0D8C8102F0; Wed, 24 Oct 2018 10:12:58 -0400 (EDT) From: Thomas Monjalon To: Kevin Laatz Cc: dev@dpdk.org, harry.van.haaren@intel.com, stephen@networkplumber.org, gaetan.rivet@6wind.com, shreyansh.jain@nxp.com, mattias.ronnblom@ericsson.com, bruce.richardson@intel.com Date: Wed, 24 Oct 2018 16:13:02 +0200 Message-ID: <2719828.p5IpHx36I6@xps> In-Reply-To: <20181024132725.5142-1-kevin.laatz@intel.com> References: <20181022110014.82153-1-kevin.laatz@intel.com> <20181024132725.5142-1-kevin.laatz@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v7 00/13] introduce telemetry library X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 14:13:01 -0000 24/10/2018 15:27, Kevin Laatz: > This patchset introduces a Telemetry library for DPDK Service Assurance. > This library provides an easy way to query DPDK Ethdev metrics. This new library is not defined as experimental. Is it on purpose? We are supposed to give an experimental period to new APIs: http://doc.dpdk.org/guides/contributing/versioning.html#general-guidelines