From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 2/3] log: add ability to match dynamic log based on shell pattern Date: Wed, 04 Apr 2018 13:34:12 +0200 Message-ID: <2341534.1pRvY70a1c@xps> References: <20180223205648.18690-1-stephen@networkplumber.org> <20180223211752.28651-1-stephen@networkplumber.org> <20180223211752.28651-3-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Stephen Hemminger To: dev@dpdk.org Return-path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 6E7EF1C178 for ; Wed, 4 Apr 2018 13:34:14 +0200 (CEST) In-Reply-To: <20180223211752.28651-3-stephen@networkplumber.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 23/02/2018 22:17, Stephen Hemminger: > Regular expressions are not the best way to match a hierarchical > pattern like dynamic log levels. And the separator for dynamic > log levels is period which is the regex wildcard character. > > A better solution is to use filename matching 'globbing' so > that log levels match like file paths. For compatibility, > use colon to separate pattern match style arguments. For > example: > --log-level 'pmd.net.virtio.*:debug' > > Signed-off-by: Stephen Hemminger > --- > +int > +rte_log_set_level_match(const char *pattern, uint32_t level) [...] > +/* set level by regular expression (using pattern match is preferred) */ > int > rte_log_set_level_regexp(const char *pattern, uint32_t level) I think "pattern" is more appropriate than "match" to differentiate from "regexp". So I suggest this function name: rte_log_set_level_pattern