From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) by dpdk.org (Postfix) with ESMTP id 51610C354 for ; Tue, 19 May 2015 16:40:28 +0200 (CEST) Received: by igbyr2 with SMTP id yr2so77386412igb.0 for ; Tue, 19 May 2015 07:40:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ws2xNWCfZQnxxdh8j1ZQqaYWya96GJv5ARQRmmo4M9s=; b=aB16rjOmXUBAJoV36PeW4B/TiiOMrXafFTKRLeCXxr+WRSvn8IR4pO4VDHpgimCZYH nSU2OV7t/yyyfdCPnk8lpFqoATd84RqEgcgnBavhQgZKN0cHwZiQLoDEUFd2oCuYJ43t +0g0Xk/psAtvyM9/9jEoMCIbV5kwEWNffdM6Pvh1szxnjIma6MUYrDsw6Gb8FHW/oXFU LoyBg+HJzgTyUxVVp0VxqorgddMt3+zwIXllJbQCx40lG5CxbYUeVbwqrZXBsz1urVTp AwVzj1V5AvhqssUHfHhsrTmJbyvqh2+y9e9hoPBpKkdEiyFv2oiC0pqhGpCZi0aYHuqE q1DA== X-Gm-Message-State: ALoCoQl5CMApnyksLIc9oOZjwJdOgPoWDiplTQ7SNt0vJi2Q2vdL4Xny20JMi8ECXia2enM4FrTi MIME-Version: 1.0 X-Received: by 10.107.164.196 with SMTP id d65mr20383962ioj.78.1432046427619; Tue, 19 May 2015 07:40:27 -0700 (PDT) Received: by 10.64.58.227 with HTTP; Tue, 19 May 2015 07:40:27 -0700 (PDT) In-Reply-To: References: <1431709707-5281-1-git-send-email-stephen@networkplumber.org> <1431709707-5281-6-git-send-email-stephen@networkplumber.org> <20150518093201.GD1636@bricha3-MOBL3> <20150518093956.0e5411d3@urahara> Date: Tue, 19 May 2015 07:40:27 -0700 Message-ID: From: Stephen Hemminger To: David Marchand Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH 5/5] ixgbe: silence noisy log messages X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 14:40:28 -0000 We need info messages about topology etc from other components. On Tue, May 19, 2015 at 12:46 AM, David Marchand wrote: > On Mon, May 18, 2015 at 6:39 PM, Stephen Hemminger < > stephen@networkplumber.org> wrote: > >> On Mon, 18 May 2015 10:32:01 +0100 >> Bruce Richardson wrote: >> >> > For the most part, this looks fine. However, I'm unsure about changing >> the log >> > level of the messages stating what the RX and TX burst functions in use >> are. I >> > would view this as important information that should generally be >> displayed as >> > the performance impacts of using a sub-optimal RX/TX code path are >> large. >> > >> > /Bruce >> >> >> At INFO level it shows up in log files that customers read. >> This is an issue where DPDK has to grow up and be ready for real world >> use, rather than being developer friendly. >> >> Our customers ask about every log message (believe me). So if there >> is no problem the drivers must be absolutely silent (STFU) >> > > Are there messages at INFO level you want to keep ? > Or can't you just set the log level (the runtime option not the build one) > to something like WARNING or ERR ? > > > -- > David Marchand > >