DPDK patches and discussions
 help / color / mirror / Atom feed
From: Karmarkar Suyash <skarmarkar@sonusnet.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1]:rte_timer:timer lag issue correction
Date: Mon, 29 Aug 2016 22:28:10 +0000	[thread overview]
Message-ID: <SN2PR03MB2271A060DF07CEAC221587EFB3E10@SN2PR03MB2271.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20160826132701.18428-1-skarmarkar@sonusnet.com>

Hello All,

Can you please review the change and let me know if any comments. I would like to push this patch to 16.07 release. Thanks

Regards
Suyash Karmarkar

-----Original Message-----
From: Karmarkar Suyash
Sent: Friday, August 26, 2016 9:27 AM
To: rsanford@akamai.com
Cc: dev@dpdk.org; Karmarkar Suyash <skarmarkar@sonusnet.com>
Subject: [PATCH v1]:rte_timer:timer lag issue correction

For Periodic timers ,if the lag gets introduced, the current code
added additional delay when the next peridoc timer was initialized
by not taking into account the delay added, with this fix the code
would start the next occurrence of timer keeping in account the
lag added.Corrected the behavior.

Fixes:rte_timer: timer lag issue

Karmarkar Suyash (1):
  Signed-off-by: Karmarkar Suyash <skarmarkar@sonusnet.com<mailto:skarmarkar@sonusnet.com>>

 lib/librte_timer/rte_timer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

 From ba885531ac26af1aabc6bd0f58d7ce744b04acf7 Mon Sep 17 00:00:00 2001
From: Karmarkar Suyash <skarmarkar@sonusnet.com<mailto:skarmarkar@sonusnet.com>>
Date: Fri, 26 Aug 2016 09:20:37 -0400
Subject: [PATCH v1] Signed-off-by: Karmarkar Suyash <skarmarkar@sonusnet.com<mailto:skarmarkar@sonusnet.com>>

---
 lib/librte_timer/rte_timer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/librte_timer/rte_timer.c b/lib/librte_timer/rte_timer.c
index 43da836..18782fa 100644
--- a/lib/librte_timer/rte_timer.c
+++ b/lib/librte_timer/rte_timer.c
@@ -613,7 +613,7 @@ void rte_timer_manage(void)
                        status.owner = (int16_t)lcore_id;
                        rte_wmb();
                        tim->status.u32 = status.u32;
-                       __rte_timer_reset(tim, cur_time + tim->period,
+                       __rte_timer_reset(tim, tim->expire + tim->period,
                                tim->period, lcore_id, tim->f, tim->arg, 1);
                        rte_spinlock_unlock(&priv_timer[lcore_id].list_lock);
                }

--
2.9.3.windows.1

  reply	other threads:[~2016-08-29 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 13:27 Karmarkar Suyash
2016-08-29 22:28 ` Karmarkar Suyash [this message]
2016-09-14 21:13 ` Karmarkar Suyash
2016-09-15  9:27   ` Pattan, Reshma
2016-09-16 15:21     ` Karmarkar Suyash
  -- strict thread matches above, loose matches on Subject: below --
2016-08-26  1:57 [dpdk-dev] [PATCH v1] rte_timer:timer " Karmarkar Suyash

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=SN2PR03MB2271A060DF07CEAC221587EFB3E10@SN2PR03MB2271.namprd03.prod.outlook.com \
    --to=skarmarkar@sonusnet.com \
    --cc=dev@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).