Thanks Reshma for the comments, the issue is a day one bug. I will correct the
fixes line and submit v2 of the patch.
-Original Message-
From: Pattan, Reshma [mailto:reshma.pat...@intel.com]
Sent: Thursday, September 15, 2016 5:28 AM
To: Karmarkar Suyash
Cc: dev at dpdk.org; thomas.mo
Hi,
>
> 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.Co
Hello,
Can you please review the change and let me know if any comments. I would like
to push this patch to 16.11 release. Thanks. Please note this fix is tested as
well.
Regards
Suyash Karmarkar
_
From: Karmarkar Suyash
Sent: Monday, August 29, 2016
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 at akamai.com
Cc: dev at dpdk.org;
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 behavio
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 behavio
6 matches
Mail list logo
