> Regards,
>> Bhanuprakash.
>>
>>> -Original Message-----
>>> From: Ilya Maximets [mailto:i.maxim...@samsung.com]
>>> Sent: Friday, August 4, 2017 2:40 PM
>>> To: ovs-dev@openvswitch.org; Bodireddy, Bhanuprakash
>>> <bhanu
gards,
> Bhanuprakash.
>
>> -Original Message-
>> From: Ilya Maximets [mailto:i.maxim...@samsung.com]
>> Sent: Friday, August 4, 2017 2:40 PM
>> To: ovs-dev@openvswitch.org; Bodireddy, Bhanuprakash
>> <bhanuprakash.bodire...@intel.com>
>>
mware.com>; Ben Pfaff <b...@ovn.org>; Aaron
>Conole <acon...@redhat.com>
>Subject: Re: [ovs-dev] [PATCH v3 00/19] Add OVS DPDK keep-alive
>functionality.
>
>Hi Bhanuprakash,
>
>Thanks for working on this.
>I have a general concern about implementation of t
Hi Bhanuprakash,
Thanks for working on this.
I have a general concern about implementation of this functionality:
*What is the profit from using rte_keepalive library ?*
Pros:
* No need to implement 'rte_keepalive_dispatch_pings()' (40 LOC)
and struct rte_keepalive (30 LOC, can be
Keepalive feature is aimed at achieving Fastpath Service Assurance
in OVS-DPDK deployments. It adds support for monitoring the packet
processing cores(PMD thread cores) by dispatching heartbeats at regular
intervals. Incase of heartbeat misses additional health checks are
enabled on the PMD thread
