From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1B3B7A0A03 for ; Sun, 17 Jan 2021 23:04:28 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CBE56140D26; Sun, 17 Jan 2021 23:04:19 +0100 (CET) Received: from CNSHJSMIN03.NOKIA-SBELL.COM (unknown [116.246.26.71]) by mails.dpdk.org (Postfix) with ESMTP id 580A4140D29 for ; Wed, 13 Jan 2021 03:38:33 +0100 (CET) X-AuditID: ac189297-0b9ff70000012f77-5a-5ffe5d204285 Received: from CNSHPPEXCH1601.nsn-intra.net (Unknown_Domain [135.251.51.101]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by CNSHJSMIN03.NOKIA-SBELL.COM (Symantec Messaging Gateway) with SMTP id C3.CD.12151.02D5EFF5; Wed, 13 Jan 2021 10:38:24 +0800 (HKT) Received: from CNSHPPEXCH1609.nsn-intra.net (135.251.51.109) by CNSHPPEXCH1601.nsn-intra.net (135.251.51.101) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Wed, 13 Jan 2021 10:38:24 +0800 Received: from CNSHPPEXCH1609.nsn-intra.net ([135.251.51.109]) by CNSHPPEXCH1609.nsn-intra.net ([135.251.51.109]) with mapi id 15.01.1979.006; Wed, 13 Jan 2021 10:38:24 +0800 From: "Li, Jiu (NSB - CN/Hangzhou)" To: "users@dpdk.org" CC: "Dong, Shaojie (NSB - CN/Hangzhou)" , "Ye, Hua (NSB - CN/Hangzhou)" , "Alasaarela, Risto (Nokia - FI/Oulu)" , "Jarvelaid, Rain (Nokia - FI/Oulu)" , "Wu, Jianyue (NSB - CN/Hangzhou)" , "Pan, Jianyong (NSB - CN/Hangzhou)" Thread-Topic: Integration from Dpdk18.05 to Dpdk19.11 - rte_timer_subsystem_init(void) Thread-Index: AdbpUl4zbAX8zLmmTsK/AswVEbWnSA== Date: Wed, 13 Jan 2021 02:38:24 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.251.51.115] MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsXS/ts4VVch9l+8weW9ShbNB9ezODB6/Fqw lDWAMYrLJiU1J7MstUjfLoEr49PDV6wFjfIVpybNZmxgnCDdxcjJISFgIjHh7FSmLkYuDiGB Q0wSPx43sEI4fxkl/j7tZYZwNjFKzNp9hwWkhU3ARuLc7w3sILaIgKrEl1l7WUCKmAUmMEss uracGSQhLBAi8W/vJqAEB1BRpMTd85IQ9XoSC85eASthAert/fCHCcTmFbCTWD7vONh8RgEx ie+n1oDFmQXEJW49mc8EcaqAxJI955khbFGJl4//sYKMlxBQkujbwARiMgukSky9GQoxUVDi 5MwnLBMYhWchGTQLoWoWkiqIEh2JBbs/sUHY2hLLFr5mhrHPHHjMhCy+gJF9FaO0s1+wh1ew r6efgbGen7+3p6NusJOrj4+es7/vJkZg1KyRmDR9B+PzWR/0DjEycTAeYpTgYFYS4S3q/hsv xJuSWFmVWpQfX1Sak1p8iFGag0VJnPfQ2c/xQgLpiSWp2ampBalFMFkmDk6pBqbri0Q3T/dM WXg4unv6Kh2h9qSk8rAXy2atOrmv4kuIb9fPPflm/Bu1w75P6mV6sUng+q3iZofY/l9ujyZv UAvIPnDSyMk4bDvXoqQIloUaldG3D/zikeucv2RKXNrznj5/DZvYycW2F5WmHFtgPOH4Yosg 4zkPVPziZFZ+4vXvTn/LwaG9/89Sh4Tzx6ImlvXtUYx9U9wXvVZJRGaxR9XJpc/27BSrWrvd eqrOk9OOmi3bl2ekH75+8eTq8949mzQNN1qkMiXHh2ZqSzCaH+0/vuBN58tL4V1VQdHr1or/ 2fWw5XLcU9bE1p/2hUfuLrRnvd+wweSF3P4T4rvM2Jl2pmzTdAmp8Ss+1p/yRlKJpTgj0VCL uag4EQDUiNWcCQMAAA== X-Mailman-Approved-At: Sun, 17 Jan 2021 23:04:17 +0100 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [dpdk-users] Integration from Dpdk18.05 to Dpdk19.11 - rte_timer_subsystem_init(void) X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hello! Dpdk experts, On Dpdk 18.05, void rte_timer_subsystem_init(void) On Dpdk 19.11, int rte_timer_subsystem_init(void) implementation change= d, which will return 0, -EALREADY or -ENOMEM; There is still have dpdk "process" mode (instead of pdkd thread mode) depl= oyment in my side. Can I have a question? If rte_timer_subsystem_init() is called one time is enough? After rte_timer_subsystem_init() called with return 0 by one process , then= other processes are able to use "rte timer" service without issue, right? Thanks in advance! Best Regards. U-Plane (Clark), Jiu LI