DPDK patches and discussions
 help / color / mirror / Atom feed
From: vuonglv@viettel.com.vn
Cc: users@dpdk.org, dev@dpdk.org
Subject: [dpdk-dev] Rx Can't receive anymore packet after received 1.5 billion packet.
Date: Mon, 17 Jul 2017 09:03:55 +0700 (ICT)	[thread overview]
Message-ID: <e8c97997-f31b-d7dc-cff3-c078cf717f40@viettel.com.vn> (raw)
In-Reply-To: <CAGSp03mc4JSykrE1iL5GJ_vPxBg+qdACormoP6_nuOhzxu3UWA@mail.gmail.com>

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

  parent reply	other threads:[~2017-07-17  2:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 12:23 [dpdk-dev] Defining multiple actions based on a field value for the same table lookup in ip_pipeline application Nidhia Varghese
2017-05-18 14:04 ` Shyam Shrivastav
2017-05-19  5:23   ` Nidhia Varghese
2017-05-19  5:37     ` Shyam Shrivastav
2017-07-17  2:03   ` vuonglv [this message]
2017-07-17 10:31     ` [dpdk-dev] Rx Can't receive anymore packet after received 1.5 billion packet Dumitrescu, Cristian
2017-07-18  1:36       ` vuonglv
2017-07-19 18:43         ` Dumitrescu, Cristian
2017-07-21 10:49           ` vuonglv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8c97997-f31b-d7dc-cff3-c078cf717f40@viettel.com.vn \
    --to=vuonglv@viettel.com.vn \
    --cc=dev@dpdk.org \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).