From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "olivier.matz@6wind.com" <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Ma, Liang J" <liang.j.ma@intel.com>,
"Mccarthy, Peter" <peter.mccarthy@intel.com>,
"santosh.shukla@caviumnetworks.com"
<santosh.shukla@caviumnetworks.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] Dynamic Logging Name Formatting
Date: Tue, 23 Jan 2018 17:31:38 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA650FF46C6@IRSMSX102.ger.corp.intel.com> (raw)
Hi All,
I'm looking at the output of app/test >> dump_log_types
There are a number of naming systems, and I think it would be good to standardize on one (before we diverge further than we already have..) Below a summary of current state, which is becoming a little messy IMO. A proposed (hopefully consistent) naming scheme suggested below that again.
Based on the suggested scheme, I think the OPDL PMD and OcteonTX would change - so adding Maintainers of those components to CC.
Feedback welcome, -Harry
=== Current State ===
=====================
Libraries:
lib.<name>
Ethdev PMDs:
pmd.<name>.info
pmd.<name>.driver
Other PMDs
pmd.<platform>.ethdev
pmd.<platform>.ethdev.init
pmd.<platform>.eventdev
pmd.<platform>.mempool
More PMDs:
eventdev.<pmd-name>.init
eventdev.<pmd-name>.driver
=== Suggested Consistent Schema ===
===================================
Libraries:
lib.<name>.specialization
Net PMDs:
pmd.<name>.specialization
// one could argue consistency would be pmd.ethdev.<name>
// but the change is larger than the value IMO - thoughts?
Eventdev PMDs:
pmd.eventdev.<name>.specialization
Crypto PMDs:
pmd.cryptodev.<name>.specialization
BBdev PMDs:
pmd.bbdev.<name>.specialization
Busses:
bus.<name>.specialization
next reply other threads:[~2018-01-23 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 17:31 Van Haaren, Harry [this message]
2018-01-23 17:45 ` Ferruh Yigit
2018-01-23 20:54 ` Bruce Richardson
2018-01-24 6:32 ` Andrew Rybchenko
2018-01-24 9:27 ` Olivier Matz
2018-01-24 9:36 ` Van Haaren, Harry
2018-01-25 9:35 ` Shreyansh Jain
2018-01-25 9:28 ` Van Haaren, Harry
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=E923DB57A917B54B9182A2E928D00FA650FF46C6@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=liang.j.ma@intel.com \
--cc=olivier.matz@6wind.com \
--cc=peter.mccarthy@intel.com \
--cc=santosh.shukla@caviumnetworks.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).