From: Olivier Matz <[email protected]>
Remove an error log in memzone_reserve_aligned_thread_unsafe().
It is up to the caller to log the error, and this is already done
in DPDK code (especially in network drivers).
Signed-off-by: Olivier Matz <olivier.matz at 6wind.com>
Acked-by: Thomas Monjalon <thomas.monjalon at 6wind.com>
---
lib/librte_eal/common/eal_common_memzone.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/lib/librte_eal/common/eal_common_memzone.c
b/lib/librte_eal/common/eal_common_memzone.c
index 5532f0d..cd60054 100644
--- a/lib/librte_eal/common/eal_common_memzone.c
+++ b/lib/librte_eal/common/eal_common_memzone.c
@@ -198,9 +198,6 @@ memzone_reserve_aligned_thread_unsafe(const char *name,
uint64_t len,
return memzone_reserve_aligned_thread_unsafe(name, len
- align,
socket_id, 0, align);
- RTE_LOG(ERR, EAL, "%s(%s, %" PRIu64 ", %d): "
- "No appropriate segment found\n",
- __func__, name, requested_len, socket_id);
rte_errno = ENOMEM;
return NULL;
}
--
1.7.10.4
