From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 399732C18; Wed, 6 Mar 2019 03:39:10 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Mar 2019 18:39:09 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,446,1544515200"; d="scan'208";a="122978803" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga008.jf.intel.com with ESMTP; 05 Mar 2019 18:39:09 -0800 Received: from fmsmsx122.amr.corp.intel.com (10.18.125.37) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 5 Mar 2019 18:39:07 -0800 Received: from bgsmsx151.gar.corp.intel.com (10.224.48.42) by fmsmsx122.amr.corp.intel.com (10.18.125.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 5 Mar 2019 18:39:07 -0800 Received: from bgsmsx101.gar.corp.intel.com ([169.254.1.171]) by BGSMSX151.gar.corp.intel.com ([169.254.3.220]) with mapi id 14.03.0415.000; Wed, 6 Mar 2019 08:09:03 +0530 From: "Varghese, Vipin" To: "Carrillo, Erik G" , "rsanford@akamai.com" CC: "dev@dpdk.org" , "techboard@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v3 0/2] Timer library changes Thread-Index: AQHUkzMMoeGGOQBc+EywnDq5KUui4qX9xqQAgACdxdA= 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> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOWYxZmEzMGQtY2YyMS00YjhhLWFjNWMtNzM2MTM3Yjc0YjgwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTURjRnBHQ05ySjByNFwvbXZ6SzZxYkp4dnZFWE5pRzl3WnJDWnlkVWJNekM5bUdqSEtYSTRBRksyNGZ4R3hKZGIifQ== dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.223.10.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v3 0/2] Timer library changes 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: , X-List-Received-Date: Wed, 06 Mar 2019 02:39:11 -0000 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?