From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <reshma.pattan@intel.com>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id 5A7A52904
 for <dev@dpdk.org>; Thu, 15 Sep 2016 11:27:49 +0200 (CEST)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by fmsmga104.fm.intel.com with ESMTP; 15 Sep 2016 02:27:48 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.30,338,1470726000"; d="scan'208";a="761002966"
Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59])
 by FMSMGA003.fm.intel.com with ESMTP; 15 Sep 2016 02:27:47 -0700
Received: from irsmsx156.ger.corp.intel.com (10.108.20.68) by
 IRSMSX151.ger.corp.intel.com (163.33.192.59) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Thu, 15 Sep 2016 10:27:46 +0100
Received: from irsmsx109.ger.corp.intel.com ([169.254.13.12]) by
 IRSMSX156.ger.corp.intel.com ([169.254.3.48]) with mapi id 14.03.0248.002;
 Thu, 15 Sep 2016 10:27:46 +0100
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: Karmarkar Suyash <skarmarkar@sonusnet.com>
CC: "dev@dpdk.org" <dev@dpdk.org>, "thomas.monjalon@6wind.com"
 <thomas.monjalon@6wind.com>, "rsanford@akamai.com" <rsanford@akamai.com>
Thread-Topic: [PATCH v1]:rte_timer:timer lag issue correction
Thread-Index: AQHSDszb2NoUriF6DUGW/KicAmNcZaB6R0SA
Date: Thu, 15 Sep 2016 09:27:45 +0000
Message-ID: <3AEA2BF9852C6F48A459DA490692831F01098625@IRSMSX109.ger.corp.intel.com>
References: <20160826132701.18428-1-skarmarkar@sonusnet.com>
 <BN3PR03MB143138678BF2179238574F8FB3F10@BN3PR03MB1431.namprd03.prod.outlook.com>
In-Reply-To: <BN3PR03MB143138678BF2179238574F8FB3F10@BN3PR03MB1431.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNzNhZTMwMDMtMzZiZS00OTUwLTlmMDAtYmVjZDg4ZTVhNjc3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IngxZ1JXOEk4M1dOd2pNS2hiTUhYVDBpajdaN3N2UWZaVVo5N3JLNHVSNmc9In0=
x-ctpclassification: CTP_IC
x-originating-ip: [163.33.239.181]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [PATCH v1]:rte_timer:timer lag issue correction
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2016 09:27:49 -0000

Hi,


>=20
> For Periodic timers ,if the lag gets introduced, the current code added a=
dditional
> delay when the next peridoc timer was initialized by not taking into acco=
unt the
> delay added, with this fix the code would start the next occurrence of ti=
mer
> keeping in account the lag added.Corrected the behavior.
>=20
> Fixes:rte_timer: timer lag issue

Fixes line format is not corerct. Fixes line should contain  commit hash th=
at introduced the bug and its subject line. For your case below should be a=
dded.

Fixes: 9b15ba89 ("timer: use a skip list")

Thanks,
Reshma