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 F322CA0546 for ; Mon, 8 Mar 2021 11:16:49 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 79B204068A; Mon, 8 Mar 2021 11:16:49 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mails.dpdk.org (Postfix) with ESMTP id 8BCA740141 for ; Mon, 8 Mar 2021 11:16:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1615198607; 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=iLvAbM5irW1CEXe31XIwH70yjj9W4rIzN+UWWHOGB+M=; b=BgRK0ZwlBiumNlwwYISAVAywDe0Jk40+Xpj/F0pjpqR49ejsuWFXtAAx4IoapOeLBlPcNd ViK2KxlUHBp6D+ezzDyuedYHq8sWZ1XTcN6CyEQOu6CEMwNBvRNEgeLlCR6KAYRmrZCAeW T99No4b+XhwARPR5K1+pGIskh3La3QY= Received: from mail-vs1-f69.google.com (mail-vs1-f69.google.com [209.85.217.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-220-ulxWdkjFOMmBfDBjP-mI3A-1; Mon, 08 Mar 2021 05:16:46 -0500 X-MC-Unique: ulxWdkjFOMmBfDBjP-mI3A-1 Received: by mail-vs1-f69.google.com with SMTP id m22so3828752vsr.4 for ; Mon, 08 Mar 2021 02:16:46 -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=iLvAbM5irW1CEXe31XIwH70yjj9W4rIzN+UWWHOGB+M=; b=bk2fPhHz1OnQq0Zz4oJC674MLfVJ/8y9b8RE/JCSmybKG0lJobYYLQjqjsmH1o1YPP Uga8uGYergMNEb8Tsuqjy+fFI2L9TAkBgXtR14sb0gBfx90tirVJJ/muLxP/EbjGUaTP iMzkkCFSkIvpCtSbtHDt+D99zoMxoaVpYqyQTHWjZVuO8IQSoa79/oAkZwd+Pd0uaqF3 zljUwudvqc/NFWQvGnGhLkkbFeQLkAB+991XgQF304XjRB7YwcYUkyEEKDa6R2YJ2puV PYgwOHtPGc58e+h6v4Ngbyl/P/VAvnZO+rJzrbjAkltoMVEJk4l1hHV/hP6XgaVIOCPb gccQ== X-Gm-Message-State: AOAM533SKR3d56i1TMHv6+LBVrKT6QJkGWJi8IFwUTzyg77mCchAopR7 L8SMUrigwcgj5ze90N6nSHb7F0J7g5npjqeemkUW6tuKxIX4y7xpPsS+UWI5E6WvNWYYwWRC8UB xHJ8yz4aLrA7nwcAp+3Rutg== X-Received: by 2002:a67:d210:: with SMTP id y16mr12738149vsi.17.1615198605403; Mon, 08 Mar 2021 02:16:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJw9rZ4ljuY8uSJs4jSDmE0ce76NnTaJC1/OlMs8iGy4lB4wZnVgMSXy/xyNDMa9U50JQ3nFT/Yd+b6KLXBjeWA= X-Received: by 2002:a67:d210:: with SMTP id y16mr12738143vsi.17.1615198605072; Mon, 08 Mar 2021 02:16:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Mon, 8 Mar 2021 11:16:34 +0100 Message-ID: To: Pinak Tripathy Cc: "users@dpdk.org" 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-users] Problem in dpdk mpool initialization in dpdk20.11 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" On Mon, Mar 8, 2021 at 9:42 AM Pinak Tripathy wrote: > I am porting the application from dpdk 17.11 to dpdk 20.11 > Application uses centos7.9 and melanox 5.2.2 PMD > > Below api call works fine in dpdk17.11 but fails in dpdk20.11 > > rte_pktmbuf_pool_create ("mbuf_pool_0", (4096 * 64 * 16 - 1), 512, 0, RTE_MBUF_DEFAULT_BUF_SIZE) fails with error no 22 (EINVAL) > -MBUF: error setting mempool handler > -PANIC in app_init_mbuf_pools(): > -Cannot create mbuf pool on socket 0 (errno=22) > > On adding debug trace found that rte_mempool_ops_table.num_ops =0. > > Not sure what is causing this issue. Can you please point out likely cause of this? This is likely a problem with loading mempool drivers. Does adding "-d /path/to/librte_mempool_ring.so" to your EAL options help with this issue? -- David Marchand