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 7969AA0A02; Thu, 25 Mar 2021 17:14:16 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3C889140E7C; Thu, 25 Mar 2021 17:14:16 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id 19AEC140E7A for ; Thu, 25 Mar 2021 17:14:14 +0100 (CET) IronPort-SDR: MmBVxEZc74SJA7bBhepuzw5W6/SEL/K5nRU+13EWb4IDIxHga97Ukij5GPsqoRKzKi3EkgzAX5 SXtALgdOsUBA== X-IronPort-AV: E=McAfee;i="6000,8403,9934"; a="254960924" X-IronPort-AV: E=Sophos;i="5.81,277,1610438400"; d="scan'208";a="254960924" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Mar 2021 09:14:13 -0700 IronPort-SDR: 4lLGWZsYG9fIwXIKBRRTGuv3eRAatV4YfsUn2pam7oKy3jw6riqUrJaslgToV+Rcv4fYDASYqL WvZziogaUItQ== X-IronPort-AV: E=Sophos;i="5.81,277,1610438400"; d="scan'208";a="514696546" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.15.70]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 25 Mar 2021 09:14:12 -0700 Date: Thu, 25 Mar 2021 16:14:08 +0000 From: Bruce Richardson To: Stephen Hemminger Cc: David Marchand , "Burakov, Anatoly" , dev , Hemant Agrawal Message-ID: <20210325161408.GC1589@bricha3-MOBL.ger.corp.intel.com> References: <20210114071346.18235-1-hemant.agrawal@nxp.com> <20210325090551.6c704060@hermes.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210325090551.6c704060@hermes.local> Subject: Re: [dpdk-dev] [PATCH] tailq: secondary process may not have all tailq available X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Mar 25, 2021 at 09:05:51AM -0700, Stephen Hemminger wrote: > On Thu, 25 Mar 2021 15:16:47 +0100 > David Marchand wrote: > > > On Mon, Jan 18, 2021 at 6:55 AM Hemant Agrawal > > wrote: > > > On 1/14/2021 7:14 PM, David Marchand wrote: > > > > On Thu, Jan 14, 2021 at 8:24 AM Hemant Agrawal wrote: > > > >> Secondary process may not have all the tailq available for > > > >> mapping, so better to ignore the error. > > > >> > > > >> e.g. if the primary process is linked with N libs > > > >> and secondary process is linked with less number of libs. > > > >> > > > >> dpdk-procinfo results into following error: > > > >> EAL: Cannot initialize tailq: VMBUS_RESOURCE_LIST > > > > For dpdk-procinfo to complain about vmbus, it means the bus driver has > > > > been loaded in the secondary, but not in the primary. > > > > Is this what you intend to do? > > > > > > > Yes. > > > > > > Typically the customer applications are built/linked with only limited > > > number of bus, devices > > > > > > dpdk-procinfo is getting compiled with default list as part of dpdk > > > build. so, if customer is trying to use the default dpdk-procinfo with > > > their application - there will be differences. > > > > > > > Is this a usecase that we support or we want to support? > > Thanks. > > > > > > Primary and secondary process have to be built with same DPDK version > and same configuration values. I'd like to see support for the information provided by proc-info also exposed via telemetry callbacks, which would give us an easier way for tooling to request and process this data. Relying on something using the multi-process model is always going to have potential issues. /Bruce