From: Rasesh Mody <rasesh.mody@qlogic.com>
To: Remy Horton <remy.horton@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Dept-Eng DPDK Dev <Dept-EngDPDKDev@qlogic.com>,
Harish Patil <harish.patil@qlogic.com>
Subject: Re: [dpdk-dev] [PATCH v4 2/3] bnx2x: enhance stats get
Date: Wed, 11 May 2016 00:58:48 +0000 [thread overview]
Message-ID: <BY1PR11MB0151DE272112AF767B015FE785720@BY1PR11MB0151.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5731B775.3080302@intel.com>
> From: Remy Horton [mailto:remy.horton@intel.com]
> Sent: Tuesday, May 10, 2016 3:27 AM
>
>
> On 07/05/2016 01:14, Rasesh Mody wrote:
> [..]
> >>> Enhance the stats_get() routine to display drop counters under
> >>> imissed counter.
> >>> Added extended stats get support to provide additional info.
> >>> Encorporated review comment to rename some of the stats.
> [..]
> > We shall split this patch into an enhancement and a bug fix.
>
> Keep in mind that the xstats API is changing so that stats_get() no longer
> includes strings:
>
> http://thread.gmane.org/gmane.comp.networking.dpdk.devel/37079
> http://thread.gmane.org/gmane.comp.networking.dpdk.devel/37571
>
> ..Remy
Sure, made a note of it. Do we know when will these changes be picked up? We can incorporate the related changes into our patches if the patches are about to be accepted.
next prev parent reply other threads:[~2016-05-11 0:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 5:38 [dpdk-dev] [PATCH v4 1/3] bnx2x: refactor Tx routine for single doorbell mechanism Rasesh Mody
2016-05-04 5:38 ` [dpdk-dev] [PATCH v4 2/3] bnx2x: enhance stats get Rasesh Mody
2016-05-06 14:47 ` Bruce Richardson
2016-05-07 0:14 ` Rasesh Mody
2016-05-10 10:27 ` Remy Horton
2016-05-11 0:58 ` Rasesh Mody [this message]
2016-06-21 9:00 ` Remy Horton
2016-05-04 5:38 ` [dpdk-dev] [PATCH v4 3/3] bnx2x: update PMD version to 1.0.1.1 Rasesh Mody
2016-05-06 14:45 ` [dpdk-dev] [PATCH v4 1/3] bnx2x: refactor Tx routine for single doorbell mechanism Bruce Richardson
2016-05-11 5:41 ` Harish Patil
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=BY1PR11MB0151DE272112AF767B015FE785720@BY1PR11MB0151.namprd11.prod.outlook.com \
--to=rasesh.mody@qlogic.com \
--cc=Dept-EngDPDKDev@qlogic.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harish.patil@qlogic.com \
--cc=remy.horton@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).