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 4E7E1A0A02; Thu, 14 Jan 2021 14:45:14 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 238EE14128F; Thu, 14 Jan 2021 14:45:14 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 69FC114128C for ; Thu, 14 Jan 2021 14:45:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610631911; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=YRMaKkvo2eo7YO3sKYTgut2lwFfdpgBlS4t/vjhe1GA=; b=QJLbfS+KHrzWaQHFSRKZZFnGmnQExeSf3zw3Wnb9DwpQCj4DFVdJwwKXoFZuaxoRiGw+Wl GV3lHSBpvN/RShGAsbizkzl5hNW8sGbEuCsCLwYt8/TTlMsX9qRKgqo1zQIrBqHP5MDnSS XO48/71s9KKL2UgQnvxhw8Ff7JXG9RI= Received: from mail-vk1-f200.google.com (mail-vk1-f200.google.com [209.85.221.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-93-egBbNJ2EPU-CXTKSVK11zw-1; Thu, 14 Jan 2021 08:45:10 -0500 X-MC-Unique: egBbNJ2EPU-CXTKSVK11zw-1 Received: by mail-vk1-f200.google.com with SMTP id j67so2333256vkh.15 for ; Thu, 14 Jan 2021 05:45:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YRMaKkvo2eo7YO3sKYTgut2lwFfdpgBlS4t/vjhe1GA=; b=i99OOzdyEkRO8IaEZ8FGJpioxxjT6Lpe9Vmi8G+X2wT+KOZ5/w8fK9u9W++vrvmqMC qVMRXLapVsZUrVGnfBQTGg0NxiggnPV3NCSbE88QPDx3N6NiGHbzXmFJP493JF6450JM KVey3dfK3vbIrp0e0k+WE8zc4tRxqZyG2dzzmpoSF4sbdxejq1IADj8Tzb2euVH8xuuu GBSy5cQyEjfV6NOxUvAg5pTLdaO8E5rJLkqkY4MBJia3A3gnnOjdq7m2Qf9Yi1KpxsOs Zmt1giSIb1XUqf6lKEMsRbk1KPRDozqE0N5zrJLxRCfz1CdtM6qdbOUUhGgKOVhQes2i cy/A== X-Gm-Message-State: AOAM532mdhO1ZXYMNbl1yUV4D40vZhQZzgAxf1dbdE0tzyAqcG8IuNKQ ZhLkDECd5dt6HzdwG2tFCAuGtpCTA8jcis009os0Pss7TH9SgtTVAin69oWLwRFY9b8GAJeu8ms p8nNSQ7Ga8Ba+B5b/NAs= X-Received: by 2002:a05:6102:21cd:: with SMTP id r13mr6463127vsg.5.1610631909961; Thu, 14 Jan 2021 05:45:09 -0800 (PST) X-Google-Smtp-Source: ABdhPJwhMegUMZJYf8Yzc7WPaE9zMJj5+FVyfMeZ734ZeFrKpgqf7srKl3qQc2BVfJRLMeo0cp+Fq6FqjikofS/Rp7g= X-Received: by 2002:a05:6102:21cd:: with SMTP id r13mr6463107vsg.5.1610631909770; Thu, 14 Jan 2021 05:45:09 -0800 (PST) MIME-Version: 1.0 References: <20210114071346.18235-1-hemant.agrawal@nxp.com> In-Reply-To: <20210114071346.18235-1-hemant.agrawal@nxp.com> From: David Marchand Date: Thu, 14 Jan 2021 14:44:58 +0100 Message-ID: To: Hemant Agrawal Cc: dev , "Burakov, Anatoly" , Bruce Richardson Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" 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, 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? -- David Marchand