From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 0/6] net/sfc: implement dynamic logging Date: Thu, 25 Jan 2018 22:38:51 +0100 Message-ID: <56198984.NQf2azoMJa@xps> References: <1516899647-8541-1-git-send-email-arybchenko@solarflare.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Olivier Matz To: Andrew Rybchenko Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id A11C52BE1 for ; Thu, 25 Jan 2018 22:39:34 +0100 (CET) In-Reply-To: <1516899647-8541-1-git-send-email-arybchenko@solarflare.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 25/01/2018 18:00, Andrew Rybchenko: > 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. Would it be possible to consider EAL patch for 18.05, and others for 18.02?