DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kiran KN <kirankn@juniper.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "chas3@att.com" <chas3@att.com>,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Min Hu (Connor)" <humin29@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] net/bonding: LACP Packet statistics support
Date: Tue, 13 Oct 2020 15:59:57 +0100	[thread overview]
Message-ID: <00b4bc65-4ec6-4808-e638-38c454fc6576@intel.com> (raw)
In-Reply-To: <96073106-5E60-4CBC-8885-B2A6CDDD40B8@juniper.net>

On 10/10/2020 11:20 AM, Kiran KN wrote:
> net/bonding: LACP Packet statistics support
> 
> Store the LACP packets sent and received for each slave.
> This can be used for debug purposes from any DPDK application.
> 
> Signed-Off-By: Kiran K N <kirankn@juniper.net>
> 
> Change-Id: Iae82bd7d0879a4c4333a292c96d431798c56e301

No change id in the upstream patches please.

<...>

> @@ -1715,3 +1726,31 @@ rte_eth_bond_8023ad_dedicated_queues_disable(uint16_t port)
> 
>   return retval;
>   }
> +
> +uint64_t
> +rte_eth_bond_8023ad_lacp_tx_count(uint16_t port_id, uint8_t clear)
> +{
> +if(port_id > BOND_MODE_8023AD_MAX_SLAVES)
> +return -1;
> +
> +if(clear) {
> +lacpdu_tx_count[port_id] = 0;
> +return 0;
> +}
> +
> + return lacpdu_tx_count[port_id];
> +}
> +
> +uint64_t
> +rte_eth_bond_8023ad_lacp_rx_count(uint16_t port_id, uint8_t clear)
> +{
> +if(port_id > BOND_MODE_8023AD_MAX_SLAVES)
> +return -1;
> +
> +if(clear) {
> +lacpdu_rx_count[port_id] = 0;
> +return 0;
> +}
> +

Hi Kiran,

Something seems went wrong with the formatting, can you please send a new version?

Also can you please cc all bonding maintainers in next version?

      reply	other threads:[~2020-10-13 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10 10:20 Kiran KN
2020-10-13 14:59 ` Ferruh Yigit [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=00b4bc65-4ec6-4808-e638-38c454fc6576@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=chas3@att.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=kirankn@juniper.net \
    --cc=thomas@monjalon.net \
    /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).