Hi Bhanu, Bhanuprakash Bodireddy <[email protected]> writes:
> This patch is aimed at achieving Fastpath Service Assurance in > OVS-DPDK deployments. This commit adds support for monitoring the packet > processing cores(pmd thread cores) by dispatching heartbeats at regular > intervals. Incase of heartbeat miss the failure shall be detected & > reported to higher level fault management systems/frameworks. > > The implementation uses POSIX shared memory object for storing the > events that will be read by monitoring framework. keep-alive feature > can be enabled through below OVSDB settings. > > keepalive=true > - Keepalive feature is disabled by default > > keepalive-interval="50" > - Timer interval in milliseconds for monitoring the packet > processing cores. > > keepalive-shm-name="/dpdk_keepalive_shm_name" > - Shared memory block name where the events shall be updated. > > When KA is enabled, 'ovs-keepalive' thread shall be spawned that wakes > up at regular intervals to update the timestamp and status of pmd cores > in shared memory region. > > An external monitoring framework like collectd(with dpdk plugin support) > can read the status updates from shared memory. On a missing heartbeat, > the collectd shall relay the status to ceilometer service running in the > controller. Below is the high level overview of deployment model. Given this runs in-line in the fastpath, can you tell me what kind of impact it is to throughput (and possibly latency) that this series implies? -Aaron _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
