DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Harrison Ford" <ogi@myself.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Packet drop issue on DPDK-based application
Date: Sun, 26 Oct 2014 09:24:14 +0100	[thread overview]
Message-ID: <trinity-88c87ecb-2252-46ad-9957-15b985b41912-1414311853814@3capp-mailcom-lxa16> (raw)

Hi, all.
 
I am trying to write an application that is supposed to receive packets over one interface, and before forwarding them out the other, log the src and dst addresses into a database for statistical purposes. I started by modifying the l2fwd example, and everything worked perfectly until I added the database logging. After that, the number of received packets dropped to about one third of the total number of sent packets (I am able to precisely determine the number of sent packets, since I am using tcpreply to send packets from a pcap file). The database logging code is obviously slowing down the entire process, but I am not sure how to resolve this issue. I have tried increasing the RX queue size (NB_RX_DESCRIPTORS value) and the memory pool size, but nothing changed. The packets are enqueued in a ring (i.e. rte_ring) where they await logging, after which they are forwarded out without any further processing.
The application is simple enough and should be working fast enough. The incoming packet speed is aroung 50 Mbps, which is also not that fast.
The application runs on a virtual machine, and I am using a single lcore to test it. What should I try to solve this problem, and what is the best way to debug such a behaviour?
 
Thank you.
Paul

             reply	other threads:[~2014-10-26  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-26  8:24 Harrison Ford [this message]
2014-10-26 18:17 ` Jayakumar, Muthurajan

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=trinity-88c87ecb-2252-46ad-9957-15b985b41912-1414311853814@3capp-mailcom-lxa16 \
    --to=ogi@myself.com \
    --cc=dev@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).