From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 4/7] rte_sched: don't clear statistics when read
Date: Fri, 20 Feb 2015 22:01:08 +0100 [thread overview]
Message-ID: <2937997.VuavGYZbL6@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891263231B33C@IRSMSX108.ger.corp.intel.com>
2015-02-20 20:23, Dumitrescu, Cristian:
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > On Fri, 20 Feb 2015 18:32:03 +0000
> > "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com> wrote:
> >
> > > Stephen, I suggest adding a new build-time configuration option for the
> > > librte_sched library in config/common_* files:
> > > CONFIG_RTE_SCHED_STATS_CLEAR_ON_READ.
> >
> > Build time config options do not work for distributions.
>
> Why?
>
> This does not affect the API, as the new API functions are always compiled
> in, and the prototypes are not changed, and no data structures are affected.
Behaviour is an important part of the API. Think comments as part of the API.
> This only changes the behavior of certain functions, so that user can
> select which mode it needs.
When user doesn't or cannot rebuild, he has no choice.
> It also preserves backward compatibility.
>
> We have so many compilation options in config file, why is this one different?
We must remove and avoid build-time options.
The only ones which might be acceptable are the ones which allow more
performance by disabling some features.
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others
> is strictly prohibited. If you are not the intended recipient, please contact
> the sender and delete all copies.
Please ask to your administrator to remove this disclaimer.
next prev parent reply other threads:[~2015-02-20 21:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 6:13 Stephen Hemminger
2015-02-05 6:13 ` [dpdk-dev] [PATCH v2 5/7] rte_sched: don't put tabs in log messages Stephen Hemminger
2015-02-20 18:33 ` Dumitrescu, Cristian
2015-02-05 6:14 ` [dpdk-dev] [PATCH v2 6/7] rte_sched: eliminate floating point in calculating byte clock Stephen Hemminger
2015-02-16 22:44 ` Dumitrescu, Cristian
2015-02-17 16:05 ` Stephen Hemminger
2015-02-05 6:14 ` [dpdk-dev] [PATCH v2 7/7] rte_sched: rearrange data structures Stephen Hemminger
2015-02-20 18:43 ` Dumitrescu, Cristian
2015-02-05 12:43 ` [dpdk-dev] [PATCH v2 4/7] rte_sched: don't clear statistics when read Neil Horman
2015-02-23 23:51 ` Thomas Monjalon
[not found] ` <fa17ab0c3bc041b88e18d3d76a255f13@HQ1WP-EXMB11.corp.brocade.com>
2015-02-24 19:18 ` Stephen Hemminger
2015-02-24 20:06 ` Thomas Monjalon
2015-02-25 17:29 ` Dumitrescu, Cristian
2015-03-10 13:55 ` Thomas Monjalon
2015-02-09 22:48 ` Dumitrescu, Cristian
2015-02-09 22:55 ` Stephen Hemminger
2015-02-20 18:32 ` Dumitrescu, Cristian
2015-02-20 19:52 ` Stephen Hemminger
2015-02-20 20:23 ` Dumitrescu, Cristian
2015-02-20 21:01 ` Thomas Monjalon [this message]
2015-02-20 21:28 ` Dumitrescu, Cristian
2015-02-21 1:53 ` Stephen Hemminger
2015-02-23 12:06 ` Dumitrescu, Cristian
2015-02-09 23:46 ` Neil Horman
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=2937997.VuavGYZbL6@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
/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).