[dpdk-dev] [RFC 0/4] Use Google Test as DPDK unit test framework

googletest is a very nice test framework and we use it very extensively in our company(Luminate Wireless), together with gmock. I understand the resistance from the maintainers that are concerned about introducing a C++ dependency to a pure C code base. The approach we take doesn't require any cha

[dpdk-dev] [PATCH] Fix buffer overflow issue in app/test/commands.c(we add 1 extra byte for trailing \0).

Fix memleak of cmdline in app/test/test.c --- app/test/commands.c | 2 +- app/test/test.c | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/app/test/commands.c b/app/test/commands.c index 9cb9606..5dfa599 100644 --- a/app/test/commands.c +++ b/app/test/commands.c @@ -439,7 +

[dpdk-dev] Build DPDK with Google bazel

bazel(http://bazel.io) is the open sourced version of Google build tool, and it has proved itself is a nice solution for monolithic server side development. In our company, we use both to build our products and it greatly reduced the hurdle of rolling out any change because we put the whole DPDK so

[dpdk-dev] "virtual" C++ keyword used in rte_devargs.h and causes compilation error in C++

at 11:24:15PM -0800, Ming Zhao wrote: >> The code is in rte_devargs.h: >> >> rte_devargs.h: >> >> /** Used if type is RTE_DEVTYPE_VIRTUAL. */ >> struct { >> /** Driver name. */ >>

[dpdk-dev] "virtual" C++ keyword used in rte_devargs.h and causes compilation error in C++

The code is in rte_devargs.h: rte_devargs.h: /** Used if type is RTE_DEVTYPE_VIRTUAL. */ struct { /** Driver name. */ char drv_name[32]; } virtual; }; Which caused clang compiler to report err