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 0ED00A0A02; Thu, 25 Mar 2021 17:06:02 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EB0A6140E52; Thu, 25 Mar 2021 17:06:01 +0100 (CET) Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) by mails.dpdk.org (Postfix) with ESMTP id 60EE7140E4D for ; Thu, 25 Mar 2021 17:06:00 +0100 (CET) Received: by mail-pf1-f182.google.com with SMTP id c204so2537808pfc.4 for ; Thu, 25 Mar 2021 09:06:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=xICxT9IyGtVBoQ+Y0260CXAtXXeoehoqdLc8LRhs2IM=; b=yYDo7RUKi83Tn0RhY/qCiMJzXykVPnOqm48HF7I6GzEfytZfGYzE9GDwbpFOfCrtwy Lx/v/jJ8zl+EK57KgiXjUtPaR5GqTqFd7/GV42kfp5XEp2fQ8vaUj3bnj45GBBFfNDRa G+iAKzKuVQPGUn4OdjYg+p1GWw/6dA0XOfsreVDoK7P1ed3q6tDzrr55ej/2SKjzjKyH bfU9M3borlRH/263og2RzKmjkfR5mMBNaEXaQCylLIN2jSzotNCGKG7V71gN9OdVndYt JVW3hCE3r8cMQeUJP10mZIHYvTTZ+irhLGljOFiSEbFOg/k5dWC7dFg/KRhehGgwnnfF wnAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=xICxT9IyGtVBoQ+Y0260CXAtXXeoehoqdLc8LRhs2IM=; b=Dnb7/5PIvmGUnD5SIXqm/sHSLZdCUHIoLx+BYiByYkcwb0T2xbF9MJue39+jl4bq9i jNXgWoAubPzKwk3Dt+Em905rCyyPY/F7TwEEQfaQzqw19suHFQZPVujAyHVnM5tLM9BX KtBfAkwsSIS0mcW4B2mnGJ/bQOJPnFSxjINwV6U06gUnX0+U+G6PrFpGoc78ni6TyTOx 1Z3VLf9DszC88L2h9XAx2mVfH+Z2Y/QvxJQPQWb2aX2AHtZs0Th8vUrHUdQFf64PY7bK 8ZbLUTyuidaUR5B5aLyv1poxHGThBxrqKWOIuxtkzBsBlS3Og/EM3wjALfiBQbqFtQ1g PcnA== X-Gm-Message-State: AOAM532cFwfLCwWm3n5FCgBX8SPbomXQRVGw/x2OTctevge/i5B/BsAc +lg3HanZpi8kWeZ/EC12sJH35Q== X-Google-Smtp-Source: ABdhPJxYAqFj+j9M5yrKIZbksEXhGFxCnHbXj8Zx0yDun+geRiUdMieprB7x2fZmfx1YXcNGj8AtVg== X-Received: by 2002:a17:902:7407:b029:e4:9b2c:528b with SMTP id g7-20020a1709027407b02900e49b2c528bmr10703602pll.6.1616688359510; Thu, 25 Mar 2021 09:05:59 -0700 (PDT) Received: from hermes.local (76-14-218-44.or.wavecable.com. [76.14.218.44]) by smtp.gmail.com with ESMTPSA id n5sm6658789pfq.44.2021.03.25.09.05.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Mar 2021 09:05:58 -0700 (PDT) Date: Thu, 25 Mar 2021 09:05:51 -0700 From: Stephen Hemminger To: David Marchand Cc: "Burakov, Anatoly" , Bruce Richardson , dev , Hemant Agrawal Message-ID: <20210325090551.6c704060@hermes.local> In-Reply-To: References: <20210114071346.18235-1-hemant.agrawal@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 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.