diff mbox

[dpdk-dev] Question about memzone failure problem.

Message ID E295F4CE-A477-42CF-B1B5-A593706FA5C7@intel.com (mailing list archive)
State Not Applicable, archived
Headers

Commit Message

Wiles, Keith April 22, 2016, 1:51 p.m. UTC 
  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 mbox

Patch

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;