From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"'David Harton (dharton)'" <dharton@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Tahhan, Maryam" <maryam.tahhan@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce xstats api change for 16.07
Date: Wed, 6 Apr 2016 09:02:43 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6128A41B7@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1955261.zYXyGahjVu@xps13>
+ David Harton,
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Subject: Re: [dpdk-dev] [PATCH] doc: announce xstats api change for 16.07
> 2016-04-05 18:58, Harry van Haaren:
> > +* ABI change is planned for the xstats API
> Have you already submitted a RFC patch to let us have an opinion on the change?
> We need, at least, to see the structure changes.
This API break is to allow changing the API of xstats given the conversation that was on-list, as discussed in this thread:
http://thread.gmane.org/gmane.comp.networking.dpdk.devel/31728/focus=31903
The issue we are going to fix is that currently PMDs copy strings when retrieving statistics, which causes unnecessary overhead. The implementation is not decided yet, but using an int->value mapping seems logical.
The rte_eth_xstats struct size may be modified, and the API to retrieve statistics will be modified.
next prev parent reply other threads:[~2016-04-06 9:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 17:58 Harry van Haaren
2016-04-05 18:45 ` Thomas Monjalon
2016-04-06 9:02 ` Van Haaren, Harry [this message]
2016-04-06 9:22 ` Thomas Monjalon
2016-04-06 11:16 ` Van Haaren, Harry
2016-04-06 12:14 ` Thomas Monjalon
2016-04-06 13:49 ` David Harton (dharton)
2016-04-06 13:53 ` Van Haaren, Harry
2016-04-06 13:46 ` Remy Horton
2016-04-06 14:00 ` David Harton (dharton)
2016-04-06 14:25 ` Tahhan, Maryam
2016-04-07 21:36 ` 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=E923DB57A917B54B9182A2E928D00FA6128A41B7@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=dharton@cisco.com \
--cc=maryam.tahhan@intel.com \
--cc=thomas.monjalon@6wind.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).