From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id E62008D99 for ; Mon, 25 Jan 2016 09:06:11 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 25 Jan 2016 00:06:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,343,1449561600"; d="scan'208";a="897669065" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga002.jf.intel.com with ESMTP; 25 Jan 2016 00:06:10 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 25 Jan 2016 00:06:10 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.215]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.209]) with mapi id 14.03.0248.002; Mon, 25 Jan 2016 16:06:08 +0800 From: "Qiu, Michael" To: "Richardson, Bruce" , "Van Haaren, Harry" Thread-Topic: [dpdk-dev] [PATCH] eal: add function to check if primary proc alive Thread-Index: AQHRU4YjdEIiCFakoU645h1q4mhKnQ== Date: Mon, 25 Jan 2016 08:06:07 +0000 Message-ID: <533710CFB86FA344BFBF2D6802E6028622F217D9@SHSMSX101.ccr.corp.intel.com> References: <1453296322-1210-1-git-send-email-harry.van.haaren@intel.com> <533710CFB86FA344BFBF2D6802E6028622F1E7EA@SHSMSX101.ccr.corp.intel.com> <20160122173747.GB13424@bricha3-MOBL3> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH] eal: add function to check if primary proc alive X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2016 08:06:12 -0000 On 1/23/2016 1:38 AM, Richardson, Bruce wrote:=0A= > On Thu, Jan 21, 2016 at 09:02:41AM +0000, Van Haaren, Harry wrote:=0A= >>> From: Qiu, Michael=0A= >>> Sent: Thursday, January 21, 2016 6:14 AM=0A= >>> To: Van Haaren, Harry ; david.marchand@6win= d.com=0A= >>> Cc: dev@dpdk.org=0A= >>> Subject: Re: [dpdk-dev] [PATCH] eal: add function to check if primary p= roc alive=0A= >>> =0A= >>> As we could start up many primaries, how does your secondary process=0A= >>> work with them?=0A= >> When a primary process initializes, the location of the config file is i= mportant. The default is /var/run/.rte_config=0A= >>=0A= >> To run multiple primary processes, the --file-prefix=3D option is used t= o specific a custom location for the config file. Eg: --file-prefix=3Dtesti= ng /var/run/.testing_config=0A= >>=0A= >> The rte_eal_check_primary_alive(const char*) function takes a char* para= meter - this is the location of the config file that the secondary process = will wait for. Setting it to the correct value will make this secondary pro= cess wait for the corresponding primary process.=0A= >>=0A= >> Regards, -Harry=0A= > Since a given secondary process only works with a single primary process,= I'm not=0A= > sure why the user should want or need to pass in this parameter. What's t= he use=0A= > case for a secondary process wanting to know about a different primary pr= ocess?=0A= > The details of what the config file is should largely be hidden from the = user=0A= > IMHO.=0A= =0A= So using the prefix, and get the file name inside the=0A= API(--file-prefix=3Dxxx then the config file /var/run/.xxx_config), if no= =0A= perfix, then could be /var/run/.rte_config.=0A= =0A= Just a suggestion. Maybe there are better solutions .=0A= =0A= Thanks,=0A= Michael=0A= > If you want to allow a secondary to query an arbitrary primary process ca= n you=0A= > still allow a NULL string to query the default primary based on the passe= d in=0A= > file-prefix parameter (if any)?=0A= >=0A= > /Bruce=0A= >=0A= =0A=