From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by dpdk.org (Postfix) with ESMTP id 7E74C5680 for ; Tue, 19 May 2015 09:46:20 +0200 (CEST) Received: by obfe9 with SMTP id e9so5917284obf.1 for ; Tue, 19 May 2015 00:46:19 -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=bznomIAl2zRIlTRIzK4+4V1CuUkvaBLHip0amZC1lfo=; b=B89nBFhUyS5AJan2d/o1jLiss8Wds7dfqv/l0lXT15nEvUGQ3cZjk0IEGpuuI3Prmi euIxd7NIid7mlGRm7U8urob/UTPh9uWwyIE+RY5fu9H2ddkjBEE7e4zVohR1mhIpQZ+2 j1cktFGghXhPET3HruccnRzpekaye3oRiVqXU/PkeYJgctlHgwRpCrcXuFNejKEI54yT ZBguBukkmPiYAMjQRriZxgG2VG3DNGUeCCzs/9MEyja7dxcl1TpZciPZ7FGcz6A16Kbf GJY0u9Nbzdj83e03iqbMAASrntGOh0u4/ovCi2kuw4nhSC9oyWM52zBSgxVr40Z5ZNk4 tsjw== X-Gm-Message-State: ALoCoQm0+Kbqd/e9ShryFilvONQUFJsldpN6cLOdDvMORCmmC5EjJc2tOJoxZ/noANCerMcXRVIi MIME-Version: 1.0 X-Received: by 10.182.73.168 with SMTP id m8mr23256903obv.58.1432021579521; Tue, 19 May 2015 00:46:19 -0700 (PDT) Received: by 10.76.25.69 with HTTP; Tue, 19 May 2015 00:46:19 -0700 (PDT) In-Reply-To: <20150518093956.0e5411d3@urahara> 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 09:46:19 +0200 Message-ID: From: David Marchand To: Stephen Hemminger 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 07:46:21 -0000 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