From patchwork Fri Apr 22 13:51:20 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: "Wiles, Keith" X-Patchwork-Id: 12210 Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 25DDB2A5D; Fri, 22 Apr 2016 15:51:25 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 4B13F2A1A for ; Fri, 22 Apr 2016 15:51:23 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 22 Apr 2016 06:51:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,517,1455004800"; d="scan'208";a="950748917" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga001.fm.intel.com with ESMTP; 22 Apr 2016 06:51:22 -0700 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 22 Apr 2016 06:51:22 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.211]) by fmsmsx120.amr.corp.intel.com ([169.254.15.242]) with mapi id 14.03.0248.002; Fri, 22 Apr 2016 06:51:22 -0700 From: "Wiles, Keith" To: "dev@dpdk.org" Thread-Topic: Question about memzone failure problem. Thread-Index: AQHRnJ4NlDtB86gjuU6ZL8BoMTlPtg== Date: Fri, 22 Apr 2016 13:51:20 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.129.95] Content-ID: MIME-Version: 1.0 Subject: [dpdk-dev] Question about memzone failure problem. 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" I was creating a rte_ring and got a message ‘RING: Cannot reserve memory’ I track it down to me trying create a ring using the same name as another ring. The question is I tracked down the problem and in the eal_common_memzone.c file I noticed the message for the problem was using DEBUG in the log message and I think it should be ERR. Should it be ERR instead of DEBUG, if so I will send a patch? Regards, Keith diff --git a/lib/librte_eal/common/eal_common_memzone.c b/lib/librte_eal/common/eal_common_memzone.c index 711c845..89ffc12 100644 --- a/lib/librte_eal/common/eal_common_memzone.c +++ b/lib/librte_eal/common/eal_common_memzone.c @@ -142,7 +142,7 @@ memzone_reserve_aligned_thread_unsafe(const char *name, size_t len, /* zone already exist */ if ((memzone_lookup_thread_unsafe(name)) != NULL) { - RTE_LOG(DEBUG, EAL, "%s(): memzone <%s> already exists\n", + RTE_LOG(ERR, EAL, "%s(): memzone <%s> already exists\n", __func__, name); rte_errno = EEXIST; return NULL;