From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 028A0548B for ; Mon, 5 Mar 2018 16:00:16 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Mar 2018 07:00:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,427,1515484800"; d="scan'208";a="180010316" Received: from fyigit-mobl.ger.corp.intel.com (HELO [10.237.221.62]) ([10.237.221.62]) by orsmga004.jf.intel.com with ESMTP; 05 Mar 2018 07:00:14 -0800 To: Andrew Rybchenko , dev@dpdk.org Cc: Olivier Matz References: <1516899647-8541-1-git-send-email-arybchenko@solarflare.com> From: Ferruh Yigit Message-ID: <7aa8e29d-e7a0-17a8-55c4-ccc96305b0f1@intel.com> Date: Mon, 5 Mar 2018 15:00:13 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1516899647-8541-1-git-send-email-arybchenko@solarflare.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 0/6] net/sfc: implement dynamic logging X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 15:00:17 -0000 On 1/25/2018 5:00 PM, Andrew Rybchenko wrote: > Unfortunately we're a bit late with dynamic logging implementation. > So, it can wait for 18.05 release cycle if required. > > The series adds EXPERIMENTAL EAL feature which removes dependency > on EAL arguments processing and log types registration. It stores > EAL loglevel arguments in the list and adds API function to register > a new log type and pick up its value from EAL arguments. > > For us it is important since we would like to be able to control > per-device log level, e.g. pmd.net.sfc.main.0000:01:00.0. It is good idea to have device level granularity in logging, I believe other devices also would like have this, if only there would be an easy way to apply this capability to all PMDs. > > The series already follows log type names format defined recently. > > Ivan Malov (6): > eal: register log type and pick level from EAL args > net/sfc: add support for driver-wide dynamic logging > net/sfc: add support for per-port dynamic logging > net/sfc: prepare to merge init logs with main log type > net/sfc: remove dedicated init log parameter > net/sfc: add dynamic log level for MCDI messages <...>