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: Mon, 23 Apr 2018 23:08:01 +0200 Message-ID: <3970843.R7zKmtknVI@xps> References: <20180223205648.18690-1-stephen@networkplumber.org> <20180223211752.28651-3-stephen@networkplumber.org> <2341534.1pRvY70a1c@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Stephen Hemminger Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id CA2D83DC for ; Mon, 23 Apr 2018 23:08:03 +0200 (CEST) In-Reply-To: <2341534.1pRvY70a1c@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Stephen, 04/04/2018 13:34, Thomas Monjalon: > 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 Are you OK to do a v3 with this change?