Re: [ovs-dev] rte_eal_init() error when using ovs-dpdk with secondary application.

Junguk Cho writes: > Hi, Aaron. > > Thank you for reply. > > You will need to use populate this option into other_config:dpdk-extra > in the ovsdb. > > ovs-vsctl --no-wait set Open_vSwitch \ > . other_config:dpdk-extra="--base-virtaddr=..." > > -> I tried to use

Re: [ovs-dev] rte_eal_init() error when using ovs-dpdk with secondary application.

Hi, Aaron. Thank you for reply. You will need to use populate this option into other_config:dpdk-extra in the ovsdb. ovs-vsctl --no-wait set Open_vSwitch \ . other_config:dpdk-extra="--base-virtaddr=..." -> I tried to use "struct rte_memseg *m = rte_eal_get_physmem_layout()" option

Re: [ovs-dev] rte_eal_init() error when using ovs-dpdk with secondary application.

Junguk Cho writes: > Hi, > > I use ovs-dpdk (ovs-2.7, dpdk-16.11.1) with one application which talks to > ovs by using ring device and "--proc-type=secondary" (secondary processes). > It generally works well, but sometimes it shows this error. > > It seems it could not find

[ovs-dev] rte_eal_init() error when using ovs-dpdk with secondary application.

Hi, I use ovs-dpdk (ovs-2.7, dpdk-16.11.1) with one application which talks to ovs by using ring device and "--proc-type=secondary" (secondary processes). It generally works well, but sometimes it shows this error. It seems it could not find correct memory mapping in the application. 2017-06-13