From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: Dynamic Logging Name Formatting
Date: Tue, 23 Jan 2018 17:45:09 +0000
Message-ID: <f3d9188a-7df8-4e40-3f47-e7cfeb145fcf@intel.com>
References: <E923DB57A917B54B9182A2E928D00FA650FF46C6@IRSMSX102.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
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>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
 "olivier.matz@6wind.com" <olivier.matz@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga14.intel.com (mga14.intel.com [192.55.52.115])
 by dpdk.org (Postfix) with ESMTP id 59C371B1DD
 for <dev@dpdk.org>; Tue, 23 Jan 2018 18:45:12 +0100 (CET)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA650FF46C6@IRSMSX102.ger.corp.intel.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 1/23/2018 5:31 PM, Van Haaren, Harry wrote:
> === 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

+1 to suggested schema, looks good to me.