From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailfilter01.viettel.com.vn (mailfilter01.viettel.com.vn [125.235.240.53]) by dpdk.org (Postfix) with ESMTP id 547CEA10; Mon, 17 Jul 2017 04:03:06 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.40,372,1496077200"; d="scan'208";a="42779558" Received: from 125.235.240.45.adsl.viettel.vn (HELO mta2.viettel.com.vn) ([125.235.240.45]) by mailfilter01.viettel.com.vn with ESMTP; 17 Jul 2017 09:03:05 +0700 Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id 5C8CC6823ED; Mon, 17 Jul 2017 09:03:55 +0700 (ICT) Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id iiWWZYNAnoPd; Mon, 17 Jul 2017 09:03:55 +0700 (ICT) Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id 3999668285D; Mon, 17 Jul 2017 09:03:55 +0700 (ICT) X-Virus-Scanned: amavisd-new at Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id meVESzmZjdpX; Mon, 17 Jul 2017 09:03:55 +0700 (ICT) Received: from vuonglv.vttek (unknown [27.68.241.28]) by mta2.viettel.com.vn (Postfix) with ESMTPSA id 0450F6823ED; Mon, 17 Jul 2017 09:03:55 +0700 (ICT) References: Cc: users@dpdk.org, dev@dpdk.org Message-ID: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit MilterAction: FORWARD Date: Mon, 17 Jul 2017 09:03:55 +0700 (ICT) From: vuonglv@viettel.com.vn Subject: [dpdk-users] Rx Can't receive anymore packet after received 1.5 billion packet. 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: Mon, 17 Jul 2017 02:03:08 -0000 Hi DPDK team, Sorry when I send this email to both of group users and dev. But I have big problem: Rx core on my application can not receive anymore packet after I did the stress test to it (~1 day Rx core received ~ 1.5 billion packet). Rx core still alive but didn't receive any packet and didn't generate any log. Below is my system configuration: - OS: CentOS 7 - Kernel: 3.10.0-514.16.1.el7.x86_64 - Huge page: 32G: 16384 page 2M - NIC card: Intel 85299 - DPDK version: 16.11 - Architecture: Rx (lcore 1) received packet then queue to the ring ----- Worker (lcore 2) dequeue packet in the ring and free it (use rte_pktmbuf_free() function). - Mempool create: rte_pktmbuf_pool_create ( "rx_pool", /* name */ 8192, /* number of elemements in the mbuf pool */ 256, /* Size of per-core object cache */ 0, /* Size of application private are between rte_mbuf struct and data buffer */ RTE_MBUF_DEFAULT_BUF_SIZE, /* Size of data buffer in each mbuf (2048 + 128)*/ 0 /* socket id */ ); If I change "number of elemements in the mbuf pool" from 8192 to 512, Rx have same problem after shorter time (~ 30s). Please tell me if you need more information. I am looking forward to hearing from you. Many thanks, Vuong Le