On 04/25/2018 06:05 PM, Aaron Conole wrote:
> Kevin Traynor writes:
>
> Thanks for the review, Kevin!
>
>> On 04/18/2018 07:30 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-app
Kevin Traynor writes:
Thanks for the review, Kevin!
> On 04/18/2018 07:30 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 s
On 04/18/2018 07:30 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 t
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 initializatio
