From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by dpdk.org (Postfix) with ESMTP id B54625A0A for ; Mon, 18 May 2015 18:39:53 +0200 (CEST) Received: by pdbqa5 with SMTP id qa5so156197125pdb.0 for ; Mon, 18 May 2015 09:39:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=W7ErUet2YuBJ3/xRz7rFd9O37LA5HRRQKIvTtu0SHa4=; b=HFSbYar5RSh6qBqcDAvCzYtvc8R5W5VArpT5Y1ea6/8wtdkctK2oQpN2GkodJHqRj1 0HaKs3SMz/TlHuTWytUvB03ZchA1ilcxeWN8g4JrasqVhpgakWsfhCRTZZh97PPz/S7m OZ15oOhASprIt4Rrt93rjKURHjSbFzaQ0eCKDEkBR68kYEwa+l+blWLho9rzoGUeOGMB p3IxZC4NM6yW7YLOWDLVhEuwaC8RKTZXxMu8I7nkYnaKL+ecxBPLdvpXeqiEzZMqMvWF epWaNZXWWbXDkL9xooFyP7Q7F5Pig2dZvWibWMC3erM0eBLG3Ev81ehaYqdDroogYdaG KfTw== X-Gm-Message-State: ALoCoQkq+BaOAO36o1T1WZgzhlrSPgY6ZC0LiZ/w+jnKsdOD4TAlkwdqGxsCOf1z5mjvPU7a9quE X-Received: by 10.68.57.131 with SMTP id i3mr31080437pbq.130.1431967193059; Mon, 18 May 2015 09:39:53 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by mx.google.com with ESMTPSA id ia3sm10535322pbc.31.2015.05.18.09.39.52 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 May 2015 09:39:52 -0700 (PDT) Date: Mon, 18 May 2015 09:39:56 -0700 From: Stephen Hemminger To: Bruce Richardson Message-ID: <20150518093956.0e5411d3@urahara> In-Reply-To: <20150518093201.GD1636@bricha3-MOBL3> References: <1431709707-5281-1-git-send-email-stephen@networkplumber.org> <1431709707-5281-6-git-send-email-stephen@networkplumber.org> <20150518093201.GD1636@bricha3-MOBL3> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Mon, 18 May 2015 16:39:54 -0000 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)