From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] app/testpmd: log mbuf pool creation Date: Mon, 30 May 2016 21:44:43 +0200 Message-ID: <2644423.ubxL6r272Z@xps13> References: <1464609857-30162-1-git-send-email-olivier.matz@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com To: Olivier Matz Return-path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 866111C52 for ; Mon, 30 May 2016 21:44:45 +0200 (CEST) Received: by mail-wm0-f46.google.com with SMTP id z87so17843837wmh.1 for ; Mon, 30 May 2016 12:44:45 -0700 (PDT) In-Reply-To: <1464609857-30162-1-git-send-email-olivier.matz@6wind.com> 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" 2016-05-30 14:04, Olivier Matz: > Enhance the logs related to mbuf pool creation. Display an info level > log when creating the mbuf, and display the error as a string on failure. > > After the patch, we have: > > [...] > EAL: probe driver: 8086:10fb rte_ixgbe_pmd > USER1: create a new mbuf pool : n=331456, \ > size=2176, socket=0 > EAL: Error - exiting with code: 1 > Cause: Creation of mbuf pool for socket 0 failed: Cannot allocate \ > memory Yes printing the error reason is a good improvement. But why the previous line is at INFO level? It looks to be a debug.