From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Varghese, Vipin" Subject: Re: [PATCH v3 0/2] Timer library changes Date: Wed, 6 Mar 2019 02:39:03 +0000 Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D31BFAA@BGSMSX101.gar.corp.intel.com> References: <1544205180-31546-1-git-send-email-erik.g.carrillo@intel.com> <1544739996-26011-1-git-send-email-erik.g.carrillo@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" , "techboard@dpdk.org" To: "Carrillo, Erik G" , "rsanford@akamai.com" Return-path: In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Erik, Apologies if I am reaching out a bit late. Please find my query below > > This enables primary and secondary processes to modify the same timer > > list, which enables some multi-process use cases that were not > > previously possible; e.g. a secondary process can start a timer whose > > expiration is detected in a primary process running a new flavor of > timer_manage(). Does this mean the following, primary can detect the timer expire primed by= secondary. On calling new timer_manage() from primary will it invoke call = back handler of secondary? If yes, has this been tested with shared library= too?