Re: [ovs-dev] [PATCH 2/2] dpdk: reflect status and version in the database

> "Stokes, Ian" writes: > > >> The normal way of retrieving the running DPDK status involves parsing > >> log files and issuing various incantations of ovs-vsctl and > >> ovs-appctl commands to determine whether the rte_eal_init successfully > started. > >> > >> This commit

Re: [ovs-dev] [PATCH 2/2] dpdk: reflect status and version in the database

"Stokes, Ian" writes: >> The normal way of retrieving the running DPDK status involves parsing log >> files and issuing various incantations of ovs-vsctl and ovs-appctl >> commands to determine whether the rte_eal_init successfully started. >> >> This commit adds two new

Re: [ovs-dev] [PATCH 2/2] dpdk: reflect status and version in the database

> The normal way of retrieving the running DPDK status involves parsing log > files and issuing various incantations of ovs-vsctl and ovs-appctl > commands to determine whether the rte_eal_init successfully started. > > This commit adds two new records to reflect the dpdk version, and the dpdk >

Re: [ovs-dev] [PATCH 2/2] dpdk: reflect status and version in the database

On 05/03/2018 08:08 PM, Aaron Conole wrote: > The normal way of retrieving the running DPDK status involves parsing > log files and issuing various incantations of ovs-vsctl and ovs-appctl > commands to determine whether the rte_eal_init successfully started. > > This commit adds two new records

[ovs-dev] [PATCH 2/2] dpdk: reflect status and version in the database

The normal way of retrieving the running DPDK status involves parsing log files and issuing various incantations of ovs-vsctl and ovs-appctl commands to determine whether the rte_eal_init successfully started. This commit adds two new records to reflect the dpdk version, and the dpdk