From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 2CDDA919B for ; Fri, 22 Jan 2016 18:37:51 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP; 22 Jan 2016 09:37:52 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,332,1449561600"; d="scan'208";a="887108999" Received: from bricha3-mobl3.ger.corp.intel.com ([10.24.26.66]) by fmsmga001.fm.intel.com with SMTP; 22 Jan 2016 09:37:48 -0800 Received: by (sSMTP sendmail emulation); Fri, 22 Jan 2016 09:37:48 -0700 Date: Fri, 22 Jan 2016 09:37:48 -0800 From: Bruce Richardson To: "Van Haaren, Harry" Message-ID: <20160122173747.GB13424@bricha3-MOBL3> References: <1453296322-1210-1-git-send-email-harry.van.haaren@intel.com> <533710CFB86FA344BFBF2D6802E6028622F1E7EA@SHSMSX101.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) 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: Fri, 22 Jan 2016 17:37:51 -0000 On Thu, Jan 21, 2016 at 09:02:41AM +0000, Van Haaren, Harry wrote: > > From: Qiu, Michael > > Sent: Thursday, January 21, 2016 6:14 AM > > To: Van Haaren, Harry ; david.marchand@6wind.com > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH] eal: add function to check if primary proc alive > > > > As we could start up many primaries, how does your secondary process > > work with them? > > When a primary process initializes, the location of the config file is important. The default is /var/run/.rte_config > > To run multiple primary processes, the --file-prefix= option is used to specific a custom location for the config file. Eg: --file-prefix=testing /var/run/.testing_config > > The rte_eal_check_primary_alive(const char*) function takes a char* parameter - 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 process wait for the corresponding primary process. > > Regards, -Harry Since a given secondary process only works with a single primary process, I'm not sure why the user should want or need to pass in this parameter. What's the use case for a secondary process wanting to know about a different primary process? The details of what the config file is should largely be hidden from the user IMHO. If you want to allow a secondary to query an arbitrary primary process can you still allow a NULL string to query the default primary based on the passed in file-prefix parameter (if any)? /Bruce