On Tue, 3 Sep 2019 10:21:17 +0530 Suraj R Gupta <surajrgu...@iith.ac.in> wrote:
> These are the links to Timers documentation. > https://doc.dpdk.org/api/rte__timer_8h.html > https://doc.dpdk.org/guides/prog_guide/timer_lib.html > > As per my understanding of the documentation, > PENDING means timer is scheduled to run but not started.(in a list) > RUNNING means timer is presently running. > STOPPED means timer has stopped and callback processed. > > rte_timer_stop() can be used from callbacks for stopping the timer even in > case of periodical(multishot timers) > my use case is for a single shot , where i have to stop the timer in middle. > rte_timer_manage is what that drives running timers. You can't stop a timer in the middle through DPDK. But you could set a flag on one cpu and test that in what ever long running loop you have in a the timer. Having a long running loop, kind of defeats the purpose of rte_timers which are meant for short running callbacks.
