DPDK patches and discussions
 help / color / mirror / Atom feed
From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: "Jain, Neeraj 3. (NSN - IN/Bangalore)" <neeraj.3.jain@nsn.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] L2FWD Sample Application stops receiving packets after	sometime
Date: Fri, 21 Mar 2014 13:35:59 +0530	[thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C61FB34757E@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
In-Reply-To: <2AA69572D8087D4FA7345FB70631D59A1FD71503@SGSIMBX007.nsn-intra.net>

Hi Neeraj,

I am glad your usecase works.

Please do let me know  what is the maximum throughput you are able to achieve with vmxnet3 (assuming your underlying physical NIC is 10 Gig), it will be interesting to see the performance.

Regards
-Prashant


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jain, Neeraj 3. (NSN - IN/Bangalore)
Sent: Thursday, March 20, 2014 5:00 PM
To: dev@dpdk.org
Subject: Re: [dpdk-dev] L2FWD Sample Application stops receiving packets after sometime

Found the Problem. Few packet buffers were not being freed which lead to slow leak of mbufs.

~Neeraj

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ext Jain, Neeraj 3. (NSN - IN/Bangalore)
Sent: Thursday, March 20, 2014 2:42 PM
To: dev@dpdk.org
Subject: [dpdk-dev] L2FWD Sample Application stops receiving packets after sometime

Hi,
I am currently running few trials with DPDK sample application for one of my project requirements. Below are the system details under which the sample application (L2 Forward) is being run.

Platform: Linux 2.6.32-358.17.1.el6.x86_64
VMWare: ESXI 5.1
Driver: vmxnet3-usermap

L2 FWD program is being run with a load of ~100K packets per second on RX queue. The sample application successfully forwards the packets to other end for some time. However, after around 1 hour run, I see that rte_eth_rx_burst returns 0 packets received, though the load generator continuously sends packet to the L2 FWD program.
The statistics reported by the sample application also shows the "Packets received:" value stops incrementing.
I also used "rte_eth_stats_get" api to check if any packets are being received on the interface. This api shows the packets are being received at the interface, however rte_eth_rx_burst does not pick these packets.

Can you please help me as to why this behavior is seen. Also, please let me know if you need further details. Thanks

~Neeraj





===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================

      reply	other threads:[~2014-03-21  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20  9:11 Jain, Neeraj 3. (NSN - IN/Bangalore)
2014-03-20 11:29 ` Jain, Neeraj 3. (NSN - IN/Bangalore)
2014-03-21  8:05   ` Prashant Upadhyaya [this message]

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=C7CE7EEF248E2B48BBA63D0ABEEE700C61FB34757E@GUREXMB01.ASIAN.AD.ARICENT.COM \
    --to=prashant.upadhyaya@aricent.com \
    --cc=dev@dpdk.org \
    --cc=neeraj.3.jain@nsn.com \
    /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).