From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id D14172B87; Wed, 6 Mar 2019 16:15:42 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Mar 2019 07:15:41 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,448,1544515200"; d="scan'208";a="324762724" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga006.fm.intel.com with ESMTP; 06 Mar 2019 07:15:41 -0800 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 6 Mar 2019 07:15:41 -0800 Received: from fmsmsx115.amr.corp.intel.com ([169.254.4.119]) by FMSMSX110.amr.corp.intel.com ([169.254.14.202]) with mapi id 14.03.0415.000; Wed, 6 Mar 2019 07:15:40 -0800 From: "Carrillo, Erik G" To: "Varghese, Vipin" , "rsanford@akamai.com" CC: "dev@dpdk.org" , "techboard@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v3 0/2] Timer library changes Thread-Index: AQHUkzMJvS49N+XKUUSapNqGtbhbKaX+GovQgADQsICAAEvNIA== Date: Wed, 6 Mar 2019 15:15:40 +0000 Message-ID: References: <1544205180-31546-1-git-send-email-erik.g.carrillo@intel.com> <1544739996-26011-1-git-send-email-erik.g.carrillo@intel.com> <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D31BFAA@BGSMSX101.gar.corp.intel.com> In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D31BFAA@BGSMSX101.gar.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOWYxZmEzMGQtY2YyMS00YjhhLWFjNWMtNzM2MTM3Yjc0YjgwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTURjRnBHQ05ySjByNFwvbXZ6SzZxYkp4dnZFWE5pRzl3WnJDWnlkVWJNekM5bUdqSEtYSTRBRksyNGZ4R3hKZGIifQ== x-ctpclassification: CTP_NT x-originating-ip: [10.1.200.107] 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 15:15:43 -0000 > -----Original Message----- > From: Varghese, Vipin > Sent: Tuesday, March 5, 2019 8:39 PM > To: Carrillo, Erik G ; rsanford@akamai.com > Cc: dev@dpdk.org; techboard@dpdk.org > Subject: RE: [dpdk-dev] [PATCH v3 0/2] Timer library changes >=20 > Hi Erik, >=20 > Apologies if I am reaching out a bit late. Please find my query below >=20 > > > > 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 libra= ry > too? > Hi Vipin, No, with the proposed patch, the callback handler would need to be a funct= ion pointer valid in the same process that is invoking the new timer_manage= (). Thanks, Gabriel