From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: The use of --log-level and its default state Date: Fri, 05 Jun 2015 12:00:30 +0200 Message-ID: <4143606.5Er6ccdYXp@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Wiles, Keith" Return-path: Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by dpdk.org (Postfix) with ESMTP id 6B48D5A0F for ; Fri, 5 Jun 2015 12:01:23 +0200 (CEST) Received: by wifx6 with SMTP id x6so15097092wif.0 for ; Fri, 05 Jun 2015 03:01:23 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-05-27 15:10, Wiles, Keith: > I would like to have the log-level default changed to not log everything, > but the user needs to enable the log messages if he needs to see more > information. Normally applications or systems are not so verbose, but if > needed the user enables the verbose or debug messages. > > Can we change the default logs and messages to be non-verbose instead? Do you mean changing this line? /* default value from build option */ internal_cfg->log_level = RTE_LOG_LEVEL; It means using the most verbose level available in the build. Maybe we should set RTE_LOG_NOTICE or RTE_LOG_WARNING, However, there is already --log-level for the user and rte_set_log_level() for the application developper. So this default log level is only used for DPDK trials and development. Probably that being verbose is a good option for such cases?