DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tahhan, Maryam" <maryam.tahhan@intel.com>
To: "Korynkevych, RomanX" <romanx.korynkevych@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Korynkevych, RomanX" <romanx.korynkevych@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] proc-info: added collectd-format and host-id	options.
Date: Fri, 3 Mar 2017 13:31:34 +0000	[thread overview]
Message-ID: <1A27633A6DA49C4A92FCD5D4312DBF536B50CA44@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <1488385639-31471-1-git-send-email-romanx.korynkevych@intel.com>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Roman Korynkevych
> Sent: Wednesday, March 1, 2017 4:27 PM
> To: dev@dpdk.org
> Cc: Korynkevych, RomanX <romanx.korynkevych@intel.com>
> Subject: [dpdk-dev] [PATCH v3] proc-info: added collectd-format and host-id
> options.
> 
> Extended proc-info application to send DPDK port statistics to STDOUT in the
> format expected by collectd exec plugin. Added HOST ID option to identify the
> host DPDK process is running on when multiple instance of DPDK are running in
> parallel. This is needed for the barometer project in OPNFV.
> 
> Signed-off-by: Roman Korynkevych <romanx.korynkevych@intel.com>

Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>

  reply	other threads:[~2017-03-03 13:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 16:52 [dpdk-dev] [PATCH] " Roman Korynkevych
2017-02-27 14:16 ` [dpdk-dev] [PATCH v2] " Roman Korynkevych
2017-02-27 15:18   ` Van Haaren, Harry
2017-03-01 16:27   ` [dpdk-dev] [PATCH v3] " Roman Korynkevych
2017-03-03 13:31     ` Tahhan, Maryam [this message]
2017-03-03 14:23       ` Van Haaren, Harry
2017-03-10 14:32         ` Thomas Monjalon
2017-02-27 15:12 ` [dpdk-dev] [PATCH] " Van Haaren, Harry

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=1A27633A6DA49C4A92FCD5D4312DBF536B50CA44@IRSMSX106.ger.corp.intel.com \
    --to=maryam.tahhan@intel.com \
    --cc=dev@dpdk.org \
    --cc=romanx.korynkevych@intel.com \
    /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).