From: Stephen Hemminger <stephen@networkplumber.org>
To: Suraj R Gupta <surajrgupta@iith.ac.in>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] Stopping DPDK Timer [RTE-Timers]
Date: Mon, 2 Sep 2019 23:04:57 -0700 [thread overview]
Message-ID: <20190902230457.62717be8@hermes.lan> (raw)
In-Reply-To: <CAMfGv3kxddQwJZ9-d5e+0aJQfXu3BBL3EOoos91VojpTJ5VQWg@mail.gmail.com>
On Tue, 3 Sep 2019 10:21:17 +0530
Suraj R Gupta <surajrgupta@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.
prev parent reply other threads:[~2019-09-03 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 5:32 [dpdk-users] Stopping DPDK Timer [dpdk-dev] [RTE-Timers] Suraj R Gupta
2019-09-02 11:22 ` [dpdk-users] [dpdk-dev] Stopping DPDK Timer [RTE-Timers] Bruce Richardson
2019-09-02 11:42 ` Suraj R Gupta
2019-09-02 15:14 ` Bruce Richardson
2019-09-03 4:51 ` Suraj R Gupta
2019-09-03 6:04 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190902230457.62717be8@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=surajrgupta@iith.ac.in \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).