Thread (13 messages) 13 messages, 5 authors, 2016-06-13

Re: [PATCH] app/test: fix bond device name too long

From: Xu, HuilongX <hidden>
Date: 2016-06-01 03:25:25

Test case: link_bonging_autotest 
Package:dpdk.org master branch newest commit + this patch 
Test cmdline: ./x86_64-native-linuxapp-gcc/app/test -c ffff -n 1
              Exec link_bonging_autotest cmdl Test environment:
OS&kernel: dpdk-rhel72 3.10.0-327.el7.x86_64
Gcc: gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC)
Hugepage: 4096*2M
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Michal Jastrzebski
Sent: Friday, May 27, 2016 11:21 PM
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] app/test: fix bond device name too long

Bond device name was too long (grather than 32 signs) that
cause mempool allocation to fail.

Fixes: 92073ef961ee ("bond: unit tests")

Signed-off-by: Michal Jastrzebski <redacted>
  Tested-by: huilong xu [off-list ref]
quoted hunk ↗ jump to hunk
---
 app/test/test_link_bonding.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test/test_link_bonding.c b/app/test/test_link_bonding.c
index 7cbc289..eeb1395 100644
--- a/app/test/test_link_bonding.c
+++ b/app/test/test_link_bonding.c
@@ -83,7 +83,7 @@
 #define MAX_PKT_BURST			(512)
 #define DEF_PKT_BURST			(16)

-#define BONDED_DEV_NAME			("unit_test_bonded_device")
+#define BONDED_DEV_NAME			("unit_test_bond_dev")

 #define INVALID_SOCKET_ID		(-1)
 #define INVALID_PORT_ID			(-1)
--
1.7.9.5
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help