From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 021CCA0AC5 for ; Fri, 3 May 2019 23:05:25 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D50522B95; Fri, 3 May 2019 23:05:24 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 2742E29AC for ; Fri, 3 May 2019 23:05:23 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9D8DF26E3B; Fri, 3 May 2019 17:05:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 03 May 2019 17:05:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=GJCho6GWXR+2Vw5jeZp2x/GSq1MTX/2wrildTUFazfk=; b=TQiPwW77fMfi SU9qelv27wr+S8j6U681Rs+Bl72mpini4VM6OTZK9P7hoCQJiOe2X/cquiBw6HyH qQCIambYmCyqmNI2IOXcCBGoAXjlGNDs09TXgMb6NBzIKFi4sHWol8vE3ZIRca/X U9MIbI8zvayBntKTCzhjJZF5RUOJfhw= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=GJCho6GWXR+2Vw5jeZp2x/GSq1MTX/2wrildTUFaz fk=; b=HbeIgTBSYslwn6cjNJAe/uijmoYua0rPNWWoxZqHmmC34g6qvskkkf2DC zzvAG/TJ6gTF86zyGBeGKAJOjPhGBCH4ThcvXLWgxvAUfaR8gRb8rjECR/LLNT/T HHeI3GzLIPS2/kWSyNbBx/gA1SHsNf0Au8DFnVwFPwtbZUX5GFvIy6jzqLUzeeX1 IW7ATPbRryRJcKnRF6gaoYftIgbTu1Z5TiubYM9+UhJsy49Hwqnl720ODpTfqPmt xWabl3U2nudErOE4FtmJhJmWCdJBz13qoF2LtwiZ2yqpFoPcz8XFD7RCkreLHgmc 4zh9pWiibAXHcC2RbLqag6WhPGj+g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrjedugdduiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 260A2103D4; Fri, 3 May 2019 17:05:21 -0400 (EDT) From: Thomas Monjalon To: Erik Gabriel Carrillo Cc: dev@dpdk.org, rsanford@akamai.com Date: Fri, 03 May 2019 23:05:18 +0200 Message-ID: <4337158.l2JlVZRV86@xps> In-Reply-To: <1556289684-11276-1-git-send-email-erik.g.carrillo@intel.com> References: <1556289684-11276-1-git-send-email-erik.g.carrillo@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] timer: fix reset/stop in callback for new API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190503210518.zQ06jFqkCbn9q1WFTmGr7eS8TfrMP3T1eoGCEhCae24@z> 26/04/2019 16:41, Erik Gabriel Carrillo: > The rte_timer_alt_manage function should track which is the running > timer and whether or not it was updated by a callback in the priv_timer > structure that corresponds to the running lcore, so that restarting > or stopping the timer from the callback works correctly. > > Fixes: c0749f7096c7 ("timer: allow management in shared memory") > > Signed-off-by: Erik Gabriel Carrillo Applied, thanks