According to manpage, ENOBUFS error indicates that either the
input or the output queue is full. This should be considered
an error, but it is treated as an "ignore" condition. Fix the
code to report an error instead.

Fixes: bacaa2754017 ("eal: add channel for multi-process communication")
Cc: sta...@dpdk.org

Signed-off-by: Anatoly Burakov <anatoly.bura...@intel.com>
---
 lib/librte_eal/common/eal_common_proc.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/lib/librte_eal/common/eal_common_proc.c 
b/lib/librte_eal/common/eal_common_proc.c
index b46d644b3..f26a60595 100644
--- a/lib/librte_eal/common/eal_common_proc.c
+++ b/lib/librte_eal/common/eal_common_proc.c
@@ -678,11 +678,6 @@ send_msg(const char *dst_path, struct rte_mp_msg *msg, int 
type)
                        unlink(dst_path);
                        return 0;
                }
-               if (errno == ENOBUFS) {
-                       RTE_LOG(ERR, EAL, "Peer cannot receive message %s\n",
-                               dst_path);
-                       return 0;
-               }
                RTE_LOG(ERR, EAL, "failed to send to (%s) due to %s\n",
                        dst_path, strerror(errno));
                return -1;
-- 
2.17.1

Reply via email to