Hi Thadeu, Finally, I switch to Open vSwitch 2.5.1 and DPDK 2.2.0 with identical hugepage setup, and it works fine.
Using the stable version of OVS is a workaround to avoid this issue. I searched for the error messages, and they are from a patch for Jumbo Frames on Aug 9, 2016( http://openvswitch.org/pipermail/dev/2016-August/077538.html). It seems that I have to wait some time for this feature being more refined. Thanks for your help. 2016-10-26 22:04 GMT+08:00 Thadeu Lima de Souza Cascardo < casca...@redhat.com>: > On Wed, Oct 26, 2016 at 10:01:39PM +0800, Bo Sun wrote: > > Hi Thadeu, > > > > Thank you for your inspiring advice and patience. > > > > I set the brige and device as type dpdk, then I found that it's caused by > > insufficient memory. > > > > Since I get the reason, I will change NUMA memory policy and try to solve > > it. > > > > Thanks again. > > > > Here are logs: > > > > 2016-10-26T13:50:29Z|00022|dpdk|ERR|Insufficient memory to create memory > > pool for netdev dpdk0, with MTU 1500 on socket 2 > > 2016-10-26T13:50:29Z|00023|bridge|WARN|could not open network device > dpdk0 > > (Cannot allocate memory) > > > > You are welcome. I am glad you found the problem. Did you allocate enough > hugepages? > > Cascardo. > -- ----------------------------- Sincerely, Bo Sun
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
