All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Jain, Deepak K" <deepak.k.jain@intel.com>,
	"Kozak, KubaX" <kubax.kozak@intel.com>
Subject: Re: [PATCH v1 2/6] ethdev: retrieve xstats by ID
Date: Fri, 28 Apr 2017 11:09:41 +0000	[thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA612A31DD4@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20170427144240.10188-3-michalx.k.jastrzebski@intel.com>

> From: Jastrzebski, MichalX K
> Sent: Thursday, April 27, 2017 3:43 PM
> To: dev@dpdk.org
> Cc: Van Haaren, Harry <harry.van.haaren@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>;
> Kozak, KubaX <kubax.kozak@intel.com>
> Subject: [PATCH v1 2/6] ethdev: retrieve xstats by ID
> 
> From: Kuba Kozak <kubax.kozak@intel.com>
> 
> Extended xstats API in ethdev library to allow grouping of stats
> logically so they can be retrieved per logical grouping  managed
> by the application.
> Added new functions rte_eth_xstats_get_names_by_id and
> rte_eth_xstats_get_by_id using additional arguments (in compare
> to rte_eth_xstats_get_names and rte_eth_xstats_get) - array of ids
> and array of values.
> 
> doc: add description for modified xstats API
> Documentation change for new extended statistics API functions.
> The old API only allows retrieval of *all* of the NIC statistics
> at once. Given this requires a MMIO read PCI transaction per statistic
> it is an inefficient way of retrieving just a few key statistics.
> Often a monitoring agent only has an interest in a few key statistics,
> and the old API forces wasting CPU time and PCIe bandwidth in retrieving
> *all* statistics; even those that the application didn't explicitly
> show an interest in.
> The new, more flexible API allow retrieval of statistics per ID.
> If a PMD wishes, it can be implemented to read just the required
> NIC registers. As a result, the monitoring application no longer wastes
> PCIe bandwidth and CPU time.
> 
> Signed-off-by: Kuba Kozak <kubax.kozak@intel.com>

Acked-by: Harry van Haaren <harry.van.haaren@intel.com>

  reply	other threads:[~2017-04-28 11:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 14:42 [PATCH v1 0/6] Extended xstats API in ethdev library to allow grouping of stats Michal Jastrzebski
2017-04-27 14:42 ` [PATCH v1 1/6] ethdev: revert patches extending xstats API in ethdev Michal Jastrzebski
2017-04-28 11:09   ` Van Haaren, Harry
2017-04-27 14:42 ` [PATCH v1 2/6] ethdev: retrieve xstats by ID Michal Jastrzebski
2017-04-28 11:09   ` Van Haaren, Harry [this message]
2017-04-27 14:42 ` [PATCH v1 3/6] ethdev: get xstats ID by name Michal Jastrzebski
2017-04-28 11:10   ` Van Haaren, Harry
2017-04-27 14:42 ` [PATCH v1 4/6] app/proc-info: support xstats by ID and " Michal Jastrzebski
2017-04-28 11:10   ` Van Haaren, Harry
2017-04-27 14:42 ` [PATCH v1 5/6] net/e1000: support xstats by ID Michal Jastrzebski
2017-04-28 11:10   ` Van Haaren, Harry
2017-04-27 14:42 ` [PATCH v1 6/6] net/ixgbe: " Michal Jastrzebski
2017-04-28 11:10   ` Van Haaren, Harry
2017-05-01 21:34 ` [PATCH v1 0/6] Extended xstats API in ethdev library to allow grouping of stats Thomas Monjalon
2017-05-01 21:49   ` Thomas Monjalon
2017-05-01 21:50 ` Thomas Monjalon

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=E923DB57A917B54B9182A2E928D00FA612A31DD4@IRSMSX102.ger.corp.intel.com \
    --to=harry.van.haaren@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=kubax.kozak@intel.com \
    --cc=michalx.k.jastrzebski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.