From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) by dpdk.org (Postfix) with ESMTP id 984011C0B for ; Fri, 1 Feb 2019 11:55:34 +0100 (CET) Received: by mail-lj1-f174.google.com with SMTP id k19-v6so5371156lji.11 for ; Fri, 01 Feb 2019 02:55:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=ebiS5r75ZaS8vF+pb9f3HwIXN8UxT4KfgdpY4VP50QE=; b=O3fXyzEZweGeL2HMlHrwIeb/7cF9v7PuevRW49UyMzYHYsCmHjBVtcRSn1vHI3v1fT rC9k/KSts2882Q/6vByWLzi4YUDif/a2vnzrpuXc505gnJU8CcwVcKDc5XFuvOkRXBwh wBa5BhC5LloD6AZeVgZAIPpCdEwvE2l04oyLujrSr22Z1xMHuwzlZ0tHyO2G3APW5ucR IABDjeKkEfQegpyqFVvkQedhtGaTvIwW5EElRJa8dCgVX5o6+SfUx2vaWPBKt+pN8mHo qHLHlZPETwVrV+2QzuD3fCCTbPZB3XxCwWDzaSYNS0IGMU7c8LZacLt+7v5QLMtou3N8 3nxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ebiS5r75ZaS8vF+pb9f3HwIXN8UxT4KfgdpY4VP50QE=; b=UAIvYZqtRl1DmTRZ5QQq1rH8psGOKxVpc0uESkpeoJ5iHszI36fN3sgjWFZzoepoLo 5maSA6lRkiwqtphH6d3AyTRi52WemBIFuttHxz0o5CKTgEn3o8e0HbLBx/DdNS3noGIV aQCpSX2uBO2+BfJhP/wPnZS01mbpxiACTbgZv38NofUt8g0mdxthKl4XxU8c0WOJtKMW /RFX4jX0ZcUOz1Hi+XcIRZajbLIQddXxLHOEZimqr0AkpceRQnIA9cSsAfPBmLurh+zk RZhZLa5LQraQVGyk06Tf/rdyJP10Xs/mNXz57c/4B0kt5FNfSaFr3VZTTgkLOemBdnIM rlIw== X-Gm-Message-State: AJcUukeIXI2f11jC01crLdjC9Z57s+1Ris2wRSvYVIxkJSm0Ta2nkShx JA+0pY9+pOvdZ1gvTwfFGKjTHvzi8K3YzvviKJlsw8yd+iU= X-Google-Smtp-Source: ALg8bN6oJITChElyB6q84xhUzOtuI0ryvgOP5MA7e/Q/fn43JrOGxr7pvWU1Rkkue7B4/CtRS8WNhyD01mb6TLw4KgI= X-Received: by 2002:a2e:910d:: with SMTP id m13-v6mr30542578ljg.187.1549018533778; Fri, 01 Feb 2019 02:55:33 -0800 (PST) MIME-Version: 1.0 From: Manish Kumar Date: Fri, 1 Feb 2019 16:25:22 +0530 Message-ID: To: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] rte_pktmbuf_alloc stuck forever in dpdk 18.05.1 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2019 10:55:34 -0000 Hello Team, I have been trying dpdk 18.05.1 on a small project which was first written for dpdk 16.11 release. It is a primary secondary process architecture where primary process is reading from the NIC and then sending it to secondary process where I am calling rte_pktmbuf_alloc for a mempool which was created in the primary process. In dpdk 16.11 eveything is working fine, however in dpdk 18.05.1 , as soon as rte_pktmbuf_alloc API is called, it gets stuck in stack_dequeue function and keeps in that state forever. Can anybody help in identifying what could be causing it. #0 0x00007f7ef232d9e0 in stack_dequeue () from /usr/lib64/librte_mempool_stack.so.1.1 #1 0x00000000004110de in rte_mempool_ops_dequeue_bulk (n=33, obj_table=0x7f4f0c735450, mp=0x7f4f0c6fef00) at /home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:679 #2 __mempool_generic_get (cache=0x7f4f0c735440, n=1, obj_table=0x7f7ee9d41b18, mp=0x7f4f0c6fef00) at /home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1495 #3 rte_mempool_generic_get (cache=0x7f4f0c735440, n=1, obj_table=0x7f7ee9d41b18, mp=0x7f4f0c6fef00) at /home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1558 #4 rte_mempool_get_bulk (n=1, obj_table=0x7f7ee9d41b18, mp=0x7f4f0c6fef00) at /home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1591 #5 rte_mempool_get (obj_p=0x7f7ee9d41b18, mp=0x7f4f0c6fef00) at /home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1617 #6 rte_mbuf_raw_alloc (mp=0x7f4f0c6fef00) at /home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:992 #7 rte_pktmbuf_alloc (mp=0x7f4f0c6fef00) at /home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:1253 Thank you so much in advance. Thanks Manish