From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org, Rajagopalan Sivaramakrishnan <raja@juniper.net>
Subject: Re: [dpdk-dev] [PATCH v3] pipeline: add statistics for librte_pipeline
Date: Fri, 05 Jun 2015 12:30:35 +0200 [thread overview]
Message-ID: <1633235.huhZUFEmyt@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891263236E6CA@IRSMSX108.ger.corp.intel.com>
2015-05-28 19:26, Dumitrescu, Cristian:
> I think we have the following options identified so far for stats collection configuration:
>
> 1. Stats configuration through the RTE_LOG_LEVEL
> 2. Single configuration flag global for all DPDK libraries
> 3. Single configuration flag per DPDK library
>
> It would be good if Thomas and Stephen, as well as others, would reply with their preference order.
There are important design questions in these threads.
I think that the best way to come to a conclusion is to submit a design rule
- to state whether statistics must be considered as a feature or as debug,
- and to decide whether stats must be always available or disabled
globally or per-library.
It should be written in a new doc. I suggest docs/guidelines/design.rst.
Then we'll have to discuss and vote on this base. It will avoid future
discussions.
The underlying discussion is to decide if every cycle is important even if
there is a real usability drawback.
In order to reach a conclusion, it seems reasonnable to target a consensus
2 weeks after the first submission of these design rules.
Thanks Cristian to follow up.
prev parent reply other threads:[~2015-06-05 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 22:44 Rajagopalan Sivaramakrishnan
2015-05-28 19:26 ` Dumitrescu, Cristian
2015-05-28 19:50 ` Rajagopalan Sivaramakrishnan
2015-05-29 4:47 ` Ramia, Kannan Babu
2015-06-05 10:30 ` Thomas Monjalon [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=1633235.huhZUFEmyt@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=raja@juniper.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).