DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] event/sw: add queue-to-port stats
Date: Mon, 15 May 2017 09:08:55 +0530	[thread overview]
Message-ID: <20170515033854.GA21041@jerin> (raw)
In-Reply-To: <1494496586-57161-1-git-send-email-harry.van.haaren@intel.com>

-----Original Message-----
> Date: Thu, 11 May 2017 10:56:26 +0100
> From: Harry van Haaren <harry.van.haaren@intel.com>
> To: dev@dpdk.org
> CC: jerin.jacob@caviumnetworks.com, Harry van Haaren
>  <harry.van.haaren@intel.com>
> Subject: [PATCH] event/sw: add queue-to-port stats
> X-Mailer: git-send-email 2.7.4
> 
> This patch targets the next-eventdev tree.
> 
> This commit adds a new statistic to the SW eventdev PMD.
> The statistic shows how many packets were sent from a
> queue to a port. This provides information on how traffic
> from a specific queue is being load-balanced to worker cores.
> 
> Note that these numbers should be compared across all queue
> stages - the load-balancing does not try to perfectly share
> each queue's traffic, rather it balances the overall traffic
> from all queues to the ports.
> 
> The statistic is printed from the rte_eventdev_dump() function,
> as well as being made available via the xstats API.
> 
> Unit tests have been updated to expect more per-queue statistics,
> and the correctness of counts and counts after reset is verified.
> 
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>

Applied to dpdk-next-eventdev/master after removing "This patch targets
the next-eventdev tree." in the git commit log.

Thanks.

      reply	other threads:[~2017-05-15  3:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  9:56 Harry van Haaren
2017-05-15  3:38 ` Jerin Jacob [this message]

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=20170515033854.GA21041@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@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).